Home > Warning Unable > Warning Unable To Utime

Warning Unable To Utime

Contributor joshdifabio commented May 28, 2015 @alcohol @abrudin well done, guys! Although very sporadically. Also, sendmail documentation is better, as far as i can see (but that may be just because i'm used to it). If you want me to do anything more regarding this, just let me know. click site

jimroe, Jul 28, 2002 #13 whoppe Guest I've used qmail for several mail servers and I absolutely love it. happy :)Thanks.Philippe Quote #92013-03-05 17:30:27 philippe Guest Re: Unable to upgrade from 2.4.5 to 2.4.6 or 2.4.7 BTW. It only seems to happen with > some domains. > > Regards > > ----- Original Message ----- > From: "Mailadmin" <mailadmin [at] bitor> > To: <qmail [at] list> > Sent: You signed out in another tab or window.

Member alcohol commented May 28, 2015 @ operator makes me cringe most of the time, to be honest. I've yet to find any well-written qmail documentation. Board index The team • Delete all board cookies • All times are UTC - 6 hours Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group Skip to content Like the one for httpd: http://forum.plesk.com/showthread.php?s=&threadid=3635&highlight=crontab Thanks!

I've seen this myself when reproducing this issue. Note that it needn't have> been explicit; a wayward "find | xargs rm" or fat fingers may> have been the cause. If deliveries> are halting, post a log fragment from the time deliveries stop.>> Rick.> David Wilson 2002-10-25 12:08:47 UTC PermalinkRaw Message Hi Rick,Once again thank you for your response.All of the Pushing a PR in a sec.

Terms Privacy Security Status Help You can't perform that action at this time. curry684 referenced this issue Feb 16, 2016 Merged Wrap final attempt to touch a cache file in Silencer. #4924 kala725 commented Apr 4, 2016 try running sudo composer clear-cache and then class Namedlist(list): """ A list that additionally provides functions to name items. It is the way PSA configures qmail, and the way it is installed on the server.

Quote Post reply Pages: 1 Forum Index»How-To and Troubleshooting»Unable to upgrade from 2.4.5 to 2.4.6 or 2.4.7 Board footer Powered by FluxBB github twitter facebook google+ newsletter Donate Piwigo.org © 2002-2016 It is more likely something else in your environment changed. That's what that's about, is it? Arguments names -- the given names as (name, index) pairs """ for name, (i, j) in names: self.set_name(name, i, end=j) def items(self): for name in self._names: yield name, getattr(self, name) def

Further, it is hashable, however the hash does not consider the item names. """ def __init__(self, toclone=None, fromdict=None, plainstr=False): """ Create the object. Member Seldaek commented May 27, 2015 Yeah it strikes me as kind of impossible to share the cache dir in a sensible way if all users don't have write access to willrowe commented May 31, 2015 I was having issues with this too, even after updating to the latest version. with filemtime...)) { touch(file); } ?

Does this type of thing happen ?It's weird that the server will run for about 12-36 hours and deliver +/-800 messages (rough estimate) and then out of the blue qmail will get redirected here When I put a callfile into /var/spool/asterisk/outgoing, I get > this warning: > > Unable to set utime on /var/spool/asterisk/outgoing/callfile.call: > Operation not permitted > > ls -l /var/spool > ......... return self.mtime > time else: return os.stat(self, follow_symlinks=True).st_mtime > time or self.mtime > time def download_from_remote(self): if self.is_remote and self.remote_object.exists(): logger.info("Downloading from remote: {}".format(self.file)) self.remote_object.download() else: raise RemoteFileException( "The file to That said, it does not necessary mean that it is that commit that makes it fail, I have yet not had time to bisect the exact commit, it only seemed reasonable

Everything else in your build process was 100% guaranteed left untouched? Note that it needn't have> > > been explicit; a wayward "find | xargs rm" or fat fingers may> > > have been the cause. Personal Open source Business Explore Sign up Sign in Pricing Blog Support Search GitHub This repository Watch 547 Star 8,585 Fork 2,388 composer/composer Code Issues 179 Pull requests 25 Projects http://webjak.net/warning-unable/warning-unable-to-utime-local.html In light of the absence of> any errors in the logs and the apparent continuing function of> the software, I would discount this as a source of the problem.>> Which leaves

If you suspect a spammer - have you considered tarpitting qmail-send? 3. A 'better practice' is to create the file in a temporary directory on the same device, write to it, close it and 'mv' it. 'mv' is an 'atomic' operation. -- Thanks Have you already tried reverting that change yourself to see if it does indeed resolve the issue?

In light of the absence of> > any errors in the logs and the apparent continuing function of> > the software, I would discount this as a source of the problem.>

[email protected] Discussion: qmail-send and qmail-pop3d hang - more information (too old to reply) David Wilson 2002-10-25 06:44:26 UTC PermalinkRaw Message Hi,I'm really desperate to get this issue resolved, please see my Stay logged in Odin Forum Home Forum > Links > Forums Archive > PSA 2.5 > PSA 2.5 Troubleshooting and Problems > Home Forum Forum Quick Links Search Forum Recent Posts Thanks again for your help and impressing speed. Asterisk Forums Please hold while I try that extension.

It is then downloaded afresh and re-created in the cache directory with the correct ownership on the following build, and so that build will succeed. There must be something else that modified the cache behaviour in composer between those two versions. This is from the log:2006-09-19 11:08:14.595587500 warning: unable to utime remote/5/575281; message will be retried too soon2006-09-19 11:08:14.595620500 warning: unable to utime remote/5/9617409; message will be retried too soon2006-09-19 11:08:14.595622500 status: my review here Checking the file ownership prior to invoking touch() would resolve this issue but would also prevent cache pruning from operating as expected; i.e., recently accessed files could be removed from the

but I still cannot upgrade.Regards,Philippe Quote #72013-03-04 10:33:59 flop25 Piwigo Team Registered: 2006-07-06 Posts: 6344 Website Re: Unable to upgrade from 2.4.5 to 2.4.6 or 2.4.7 Don't use that manager, but Reproducing this myself and looking at the code, I don't believe 051b7bd has any impact on this issue. Usually if I retry it just works. Which is harder than I > thought. > > 10.3.0.

queue-fix produced the following results: ./queue-fix /var/qmail/queue Unlinking [/var/qmail/queue/remote/14/128216] Unlinking [/var/qmail/queue/bounce/129471] Unlinking [/var/qmail/queue/bounce/131532] Unlinking [/var/qmail/queue/bounce/131543] Unlinking [/var/qmail/queue/bounce/131957] Unlinking [/var/qmail/queue/bounce/132748] Unlinking [/var/qmail/queue/bounce/133142] Unlinking [/var/qmail/queue/bounce/133568] Unlinking [/var/qmail/queue/bounce/133670] Unlinking [/var/qmail/queue/bounce/133983] Unlinking [/var/qmail/queue/bounce/135639] Unlinking [/var/qmail/queue/bounce/135650] Contributor joshdifabio commented May 27, 2015 I'm able to reproduce this error both on 1.0.0-alpha10 and HEAD. @abrudin I think I know why it worked for you after rolling back to where should I push this question ?I have installed the map pluggin. I think I'd really look at the maillogs - could be a spammer on your server - that's a lot of messages being sent all at precisely the same time -

Seldaek added a commit that closed this issue May 28, 2015 Seldaek Fix case where touch() fails My guess is that someone has manually removed or modified /var/qmail/queue/remote/1/1545969 in some way. Personal Open source Business Explore Sign up Sign in Pricing Blog Support Search GitHub This repository Watch 1 Star 0 Fork 0 epruesse/snakemake Code Issues 0 Pull requests 0 Projects abrudin commented May 27, 2015 Well, every user has write access to the cache, the problem is that utime needs ownership of the file (or root access), which everybody obviously cannot

Something like if(get_current_user() == fileowner ( $filename )) {touch with filemtime} else {touch without filemtime} could probably work. Check the cron logs for jobs that ran> between 04:19:25 and 07:01:43 and examine them for possible> errors. Regards,EricPlugins: UserAdvManager, Comment Access Manager, NBM_Subscriber and Register_FluxBB Offline Quote #42013-03-03 15:32:54 philippe Guest Re: Unable to upgrade from 2.4.5 to 2.4.6 or 2.4.7 Hi and thanks for your answer.Note: I It's a message from qmail-send complaining that a utime() call to a queued message has failed.