abrudin commented May 28, 2015 Hello again, now I have done a git bisect to narrow down the commit that makes it fail, and it was indeed the previously mentioned commit: the multiplicity (and wildcard values) will be expanded after a certain rule has been run """ annotated = flag(value, "dynamic", True) tocheck = [annotated] if not_iterable(annotated) else annotated for file in The fact that plesk uses qmail makes me very happy whoppe, Jul 29, 2002 #14 (You must log in or sign up to reply here.) Show Ignored Content Share This It is the way PSA configures qmail, and the way it is installed on the server. http://webinweb.net/warning-unable/warning-unable-to-utime-remote.html
Perhaps there are kernel> generated log entries that might indicate a filesystem problem.> Similarly if qmail-send wasn't supposed to stop, you'll have to> determine why it got sent a TERM signal.>> Check the admin shell history (eg ~root/.bash_history)> > > for commands that may have removed files.> > >> > > If these steps turn up nothing, then it's likely to remain Jaspur commented Aug 11, 2015 @Seldaek not working. Already have an account?
Arguably this is an acceptable trade-off but I think that's @Seldaek's call. Logged mmccarn Wiki & Docs Team Offline Posts: 2,107 Qmail problems « Reply #5 on: September 20, 2006, 08:35:12 PM » Now that I look at your first post againQuote2006-09-19 11:08:14.595587500 If you suspect a spammer - have you considered tarpitting qmail-send? 3. Before commit 051b7bd it works fine, after it fails with the utime error message.
But I didn't remember what I did do to fix it. I use RedHat 7.1 with Plesk 2.5.1. We downgraded then it worked, we upgraded again it stopped working, downgraded it worked. kark, Jul 1, 2002 #3 Dominic Guest Here is the log before Qmail stop running, thanks!!!
Member Seldaek commented Aug 11, 2015 @Jaspur do you get an exception or just that line in the output and it continues? Like the one for httpd: http://forum.plesk.com/showthread.php?s=&threadid=3635&highlight=crontab Thanks! Newer Than: Search this thread only Search this forum only Display results as threads Useful Searches Recent Posts More... Is the filemtime() call failing?
How would the CRON job look like to re-start qmail every 8 hours?? What deliveries aren't working?>> > Oct 25 07:01:43 mail qmail: 1035522103.543938 warning: unable to utime> > remote/1/180160; message will be retried too soon>> There's a problem with /var/qmail/queue/remote/1/180160. It works great at the picture level (select picture then location) ... Paul Click to expand...
Member Seldaek commented May 27, 2015 So we should just do a is_writable check before doing the touch? Skip to content Wiki Blog Forums Mailing Lists Contact Us Advanced search Forums have moved to https://community.asterisk.org Board index RSS RSS Change font size FAQ Information The requested topic does not Even if you build repeatedly with 051b7bd you should see successful builds. Also, just in case you're unaware, creating the call file in the /outgoing/ directory is an invitation for a race condition.
Hopefully thiswill help.Thank you for all the assistance....if I don't come right I'll probably needto email you again.Many thanks and kind regards.David WilsonDcData+27 83 787 7424http://www.dcdata.co.zaLinuxBox S.A - Africa's largest online his comment is here Pushing a PR in a sec. I have to reboot every 10 hours to avoid that qmail stops working. Seldaek added a commit that closed this issue May 28, 2015 Seldaek
At the moment, almost none of the users actually use the server as an SMTP of POP server. Member alcohol commented May 28, 2015 The touch operation cannot be the touch root cause of your issue, because as others have mentioned, it was already present (the only thing that Well, I can't agree with that...the qmail install on all of my plesk boxes runs very very well. http://webinweb.net/warning-unable/warning-unable-to-utime-local.html 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
Dominic, Jun 30, 2002 #1 Dominic Guest It's there script and cronjob which will check if qmail is up and restart it if not? Member alcohol commented May 28, 2015 On another note, there should be some more sanity checks probably to preclude scenarios such as these from breaking the flow. Next message: [asterisk-users] Video Conference in Asterisk1.4 (using asterisk gui) Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] On Sat, 7 Apr 2012, sean
This error is characteristic of an Piwigo 2.3 using files of 2.4you should resend all files through FTP To get a better help : Politeness like Hello-A link-Your past actions precisely I'll keep in touch with the list to report the results. abrudin commented May 28, 2015 Thanks for your help! I have other qmail servers running for 6 months, with no problems, not even restarting qmail.
Check the cron logs for jobs that ran> > > between 04:19:25 and 07:01:43 and examine them for possible> > > errors. 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 Reload to refresh your session. navigate here That's what that's about, is it?
shivas commented Feb 16, 2016 composer clearcache is not an option in some jenkins or other CI tools. It makes sense now. It's only a warning and not an error and should not block the upgrade / installation process.But you've a second set of warning messages: "Warning: touch(): Utime failed:". 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
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. At this time, Piwigo is qualified for Php 5.3.That causes the "Strict Standards: Non-static method" warning. These problems are also often a symptom of a problem with the queue - like what could occur trying to remove messages manually. Arguments name -- a name index -- the item index """ self._names[name] = (index, end) if end is None: setattr(self, name, self[index]) else: setattr(self, name, Namedlist(toclone=self[index:end])) def get_names(self): """ Get the
Usually if I retry it just works. Most problems with qmail / Plesk arise because the base server or DNS is not configured correctly, or a spammer has gotten into the system either because qmail was allowed to If an exception please run with -v and paste the backtrace, just to be sure where it comes from. Logged mmccarn Wiki & Docs Team Offline Posts: 2,107 Qmail problems « Reply #1 on: September 20, 2006, 05:10:40 PM » I have one system that did this intermittently after loading
Member alcohol commented May 28, 2015 This is interesting: http://linux.die.net/man/2/utime Changing timestamps is permitted when: either the process has appropriate privileges, or the effective user ID equals the user ID of but gives me a 404 on /piwigo/map.php at the top level.Regards,Philippe Quote #102013-03-05 17:47:23 plg Piwigo Team Location: Nantes, France, Europe Registered: 2002-04-05 Posts: 12940 Website Re: Unable to upgrade from I run /etc/init.d/qmail start or /etc/init.d/qmail restart until /etc/init.d/qmail status does not say "...wants down..."(My examples all involve the command line, but the same behavior is possible when deleting messages from then restart apache.In both cases I get the same errors and no longer can use the server as I get a new error when I reload:Fatal error: Smarty error: [in mainpage_categories.tpl
Just to be clear, touch() (and the underlying utime operation, which is failing in your case) was already invoked prior to 051b7bd.