error confirmed:
i got the same error as i upgraded last night from 1.1.12 to 1.1.13.
i tried to install again on the same machine and i didn´t got this error message.
at 3 further try on the same machine the error came only once.
An error appears while upgrading the panel
-
- solved
- TheCry
- Closed
- Thread is marked as Resolved.
-
-
Hello ;
The error reported by @TheCry here was not really about policyd-weight. This was about the IP manager and the issue has been fixed.
About policy-weight
This is not an error from i-MSCP. Previously, the error was hidden. I'll see how I can handle that. Please, next time you're seeing that error, report the detailed log from /var/log/mail.log.
Thanks
-
-
...happened again on my upgrade from 1.1.13 to 1.1.14
Here are lines from mail.log
Display MoreCode- Sep 15 15:35:50 vsrv58002 authdaemond: stopping authdaemond children
- Sep 15 15:36:18 vsrv58002 postfix/policyd-weight[24508]: cache: /etc/policyd-weight.conf reloaded
- Sep 15 15:36:20 vsrv58002 authdaemond: modules="authmysql authpam", daemons=5
- Sep 15 15:36:20 vsrv58002 authdaemond: Installing libauthmysql
- Sep 15 15:36:20 vsrv58002 authdaemond: Installation complete: authmysql
- Sep 15 15:36:20 vsrv58002 authdaemond: Installing libauthpam
- Sep 15 15:36:20 vsrv58002 authdaemond: Installation complete: authpam
- Sep 15 15:37:07 vsrv58002 postfix/master[25446]: reload -- version 2.9.6, configuration /etc/postfix
- Sep 15 15:37:10 vsrv58002 postfix/master[25446]: reload -- version 2.9.6, configuration /etc/postfix
- Sep 15 15:37:11 vsrv58002 postgrey[26014]: Process Backgrounded
- Sep 15 15:37:11 vsrv58002 postgrey[26014]: 2014/09/15-15:37:11 postgrey (type Net::Server::Multiplex) starting! pid(26014)
- Sep 15 15:37:11 vsrv58002 postgrey[26014]: Resolved [localhost]:10023 to [127.0.0.1]:10023, IPv4
- Sep 15 15:37:11 vsrv58002 postgrey[26014]: Binding to TCP port 10023 on host 127.0.0.1 with IPv4
- Sep 15 15:37:12 vsrv58002 postfix/policyd-weight[24508]: cache killed
- Sep 15 15:37:12 vsrv58002 postfix/policyd-weight[26025]: warning: err: init: master: bind 12525: IO::Socket::INET: Die Adresse wird bereits verwendet Die Adresse wird bereits verwendet at /usr/sbin/policyd-weight line 1034.#012
- Sep 15 15:38:13 vsrv58002 postfix/master[25446]: terminating on signal 15
- Sep 15 15:38:14 vsrv58002 postfix/master[26951]: daemon started -- version 2.9.6, configuration /etc/postfix
- Sep 15 15:38:40 vsrv58002 postfix/pickup[26962]: 2096D921CF: uid=1000 from=<[email protected]>
- Sep 15 15:38:40 vsrv58002 postfix/cleanup[27922]: 2096D921CF: message-id=<[email protected]>
- Sep 15 15:38:40 vsrv58002 postfix/qmgr[26963]: 2096D921CF: from=<[email protected]>, size=1060, nrcpt=1 (queue active)
- Sep 15 15:38:40 vsrv58002 postfix/smtp[27924]: 2096D921CF: to=<[email protected]>, relay=mx01.emig.gmx.net[213.165.67.97]:25, delay=0.66, delays=0.09/0.03/0.18/0.36, dsn=2.0.0, status=sent (250 Requested mail action okay, completed: id=0LlHTu-1Y0w1r0uF4-00b2ZP)
- Sep 15 15:38:40 vsrv58002 postfix/qmgr[26963]: 2096D921CF: removed
- Sep 15 15:39:40 vsrv58002 pop3d: Connection, ip=[::ffff:127.0.0.1]
- Sep 15 15:39:40 vsrv58002 pop3d: Disconnected, ip=[::ffff:127.0.0.1]
- Sep 15 15:39:40 vsrv58002 imapd: Connection, ip=[::ffff:127.0.0.1]
- Sep 15 15:39:40 vsrv58002 imapd: Disconnected, ip=[::ffff:127.0.0.1], time=0
- Sep 15 15:39:40 vsrv58002 postfix/smtpd[27939]: connect from vsrv58002.my.domain.de.local[127.0.0.1]
- Sep 15 15:39:40 vsrv58002 postfix/smtpd[27939]: lost connection after CONNECT from vsrv58002.my.domain.de.local[127.0.0.1]
- Sep 15 15:39:40 vsrv58002 postfix/smtpd[27939]: disconnect from vsrv58002.my.domain.de.local[127.0.0.1]
- Sep 15 15:41:27 vsrv58002 postfix/policyd-weight[27954]: policyd-weight 0.1.15 beta-2 started and daemonized. conf:/etc/policyd-weight.conf; GID:111 111 EGID:111 111 UID:107 EUID:107; taint mode: 0
- Sep 15 15:41:27 vsrv58002 postfix/policyd-weight[27954]: cache_query: start: calling spawn_cache()
- Sep 15 15:41:27 vsrv58002 postfix/policyd-weight[27955]: cache spawned
-
@Heart1010
Again: This is not an i-MSCP bug. This issue has been fixed in the develop branch with some hacking but the fix is not part of the 1.1.14. In the 1.1.14, we are doing a simple restart which ends with error when the pid file has gone away. It's not a major issue and this explain why the fix was not integrated in the 1.1.14. -
-
Ok thanks for clarification... saw only your post above where you want detailed log and thought I post it here.