Error in Logfile

[pheck]

Hello!

In my mail.log, I see quite often the following entry by MagicSpam following a SMTP connect:

Code: Select all

Oct  6 07:31:28 h2729830 magicspam-plesk[595]: lm_sock.c:173 ERROR lm_fsock_connect(): No such file or directory [/var/run/magicspam/magicspam.sock]

Tried to search for the error code without success.

Does anyone has an idea, what this means? Could it be ignored?

Cheers Peter

[magicspam]

Hello Peter,

Thank you for your post.

In order to better assist you with this issue, could you please provide us the listing of the following directory:

ls -la /var/run/magicspam/

Also, can you please confirm if the MagicSpam daemon is running:

service magicspam-daemon status

If it is not running, try:

service magicspam-daemon start

In addition, can you please fill us in on the following information about your platform:

- MagicSpam Version

- Operating System and Version

- Operating System Architecture (32 bit or 64 bit)

- Plesk Version

- MTA (Qmail, Postfix, Exim)

Thank you Peter,

[pheck]

Hello,

OS: Ubuntu 16.04.3 LTS‬#

Code: Select all

root@h2729830:/var/log# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial

Plesk Onyx
Version 17.5.3 Update #24

MagicSpam PRO
Version: 2.1-8


Problem seems to be related to the deamon:

Code: Select all

root@h2729830:/var/log# /etc/init.d/magicspam-daemon stop
Stopping magicspam-daemon ...done
root@h2729830:/var/log# /etc/init.d/magicspam-daemon start
Starting magicspam-daemon .../usr/local/psa/admin/sbin/modules/magicspampro/magicspam-daemon: error while loading shared libraries: libdb-5.1.so: cannot open shared object file: No such file or directory
Failed to start magicspam-daemon
root@h2729830:/var/log# service magicspam-daemon start
Job for magicspam-daemon.service failed because the control process exited with error code. See "systemctl status magicspam-daemon.service" and "journalctl -xe" for details.

Code: Select all

root@h2729830:/var/log# systemctl status magicspam-daemon.service
● magicspam-daemon.service - MagicSpam AntiSpam service daemon
   Loaded: loaded (/etc/systemd/system/magicspam-daemon.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sa 2017-10-07 10:08:26 CEST; 45s ago
  Process: 13109 ExecStart=/etc/init.d/magicspam-daemon start (code=exited, status=1/FAILURE)

Okt 07 10:08:24 h2729830.stratoserver.net magicspam-daemon[13109]: Starting magicspam-daemon .../usr/local/psa/admin/sbin/modules/magicspampro/magicspam-daemon: error while loading shared libraries: libdb-5.1.so: cannot open shared object f
Okt 07 10:08:26 h2729830.stratoserver.net magicspam-daemon[13109]: Failed to start magicspam-daemon

Code: Select all

root@h2729830:/var/log# journalctl -xe|grep magic
Okt 07 09:55:01 h2729830.stratoserver.net CRON[4848]: pam_unix(cron:session): session opened for user magicspam by (uid=0)
Okt 07 09:55:01 h2729830.stratoserver.net CRON[4853]: (magicspam) CMD (find /etc/magicspam/db/queue -depth -mindepth 1 -maxdepth 1 -type f -cmin +5 -delete)
Okt 07 09:55:01 h2729830.stratoserver.net CRON[4848]: pam_unix(cron:session): session closed for user magicspam
Okt 07 10:00:01 h2729830.stratoserver.net CRON[28102]: pam_unix(cron:session): session opened for user magicspam by (uid=0)
Okt 07 10:00:01 h2729830.stratoserver.net CRON[28105]: (magicspam) CMD (find /etc/magicspam/db/queue -depth -mindepth 1 -maxdepth 1 -type f -cmin +5 -delete)
Okt 07 10:00:01 h2729830.stratoserver.net CRON[28102]: pam_unix(cron:session): session closed for user magicspam
Okt 07 10:00:13 h2729830.stratoserver.net magicspam-plesk[595]: lm_sock.c:173 ERROR lm_fsock_connect(): No such file or directory [/var/run/magicspam/magicspam.sock]
Okt 07 10:00:14 h2729830.stratoserver.net /usr/lib/plesk-9.0/psa-pc-remote[484]: SKIP during call 'magicspam-flag' handler
Okt 07 10:00:15 h2729830.stratoserver.net sendmail[29353]: plesk sendmail[29353]: SKIP during call 'magicspam-flag' handler
Okt 07 10:05:01 h2729830.stratoserver.net CRON[12910]: pam_unix(cron:session): session opened for user magicspam by (uid=0)
Okt 07 10:05:01 h2729830.stratoserver.net CRON[12913]: (magicspam) CMD (find /etc/magicspam/db/queue -depth -mindepth 1 -maxdepth 1 -type f -cmin +5 -delete)
Okt 07 10:05:01 h2729830.stratoserver.net CRON[12910]: pam_unix(cron:session): session closed for user magicspam
Okt 07 10:06:05 h2729830.stratoserver.net unknown[19409]: plesk sendmail[19409]: SKIP during call 'magicspam-flag' handler
Okt 07 10:06:51 h2729830.stratoserver.net magicspam-plesk[595]: lm_sock.c:173 ERROR lm_fsock_connect(): No such file or directory [/var/run/magicspam/magicspam.sock]
Okt 07 10:06:51 h2729830.stratoserver.net /usr/lib/plesk-9.0/psa-pc-remote[484]: SKIP during call 'magicspam-flag' handler
Okt 07 10:07:28 h2729830.stratoserver.net magicspam-daemon[11482]: Starting magicspam-daemon .../usr/local/psa/admin/sbin/modules/magicspampro/magicspam-daemon: error while loading shared libraries: libdb-5.1.so: cannot open shared object file: No such file or directory
Okt 07 10:07:30 h2729830.stratoserver.net magicspam-daemon[11482]: Failed to start magicspam-daemon
Okt 07 10:08:24 h2729830.stratoserver.net magicspam-daemon[13109]: Starting magicspam-daemon .../usr/local/psa/admin/sbin/modules/magicspampro/magicspam-daemon: error while loading shared libraries: libdb-5.1.so: cannot open shared object file: No such file or directory
Okt 07 10:08:26 h2729830.stratoserver.net magicspam-daemon[13109]: Failed to start magicspam-daemon
Okt 07 10:10:01 h2729830.stratoserver.net CRON[14692]: pam_unix(cron:session): session opened for user magicspam by (uid=0)
Okt 07 10:10:01 h2729830.stratoserver.net CRON[14695]: (magicspam) CMD (find /etc/magicspam/db/queue -depth -mindepth 1 -maxdepth 1 -type f -cmin +5 -delete)
Okt 07 10:10:01 h2729830.stratoserver.net CRON[14692]: pam_unix(cron:session): session closed for user magicspam

Ciao Peter

[pheck]

Looks like a problem with the deamon:

Code: Select all

root@h2729830:/home/eljeffe# service magicspam-daemon status
● magicspam-daemon.service - MagicSpam AntiSpam service daemon
   Loaded: loaded (/etc/systemd/system/magicspam-daemon.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Mo 2017-10-09 08:14:11 CEST; 48s ago
  Process: 403 ExecStart=/etc/init.d/magicspam-daemon start (code=exited, status=1/FAILURE)

Okt 09 08:14:09 h2729830.stratoserver.net magicspam-daemon[403]: Starting magicspam-daemon .../usr/local/psa/admin/sbin/modules/magicspampro/magicspam-daemon: error while loading shared libraries: libdb-5.1.so: cannot open shared object file: No such
Okt 09 08:14:11 h2729830.stratoserver.net magicspam-daemon[403]: Failed to start magicspam-daemon

Code: Select all

root@h2729830:/home/eljeffe# ls -la /var/run/magicspam/
total 4
drwxr-xr-x  2 magicspam magicspam  60 Okt  9 08:14 .
drwxr-xr-x 22 root      root      840 Okt  9 08:15 ..
-rw-r--r--  1 magicspam magicspam   4 Okt  9 08:14 magicspam-milter.pid

Code: Select all

root@h2729830:/home/eljeffe# service magicspam-daemon start
Job for magicspam-daemon.service failed because the control process exited with error code. See "systemctl status magicspam-daemon.service" and "journalctl -xe" for details.

Code: Select all

root@h2729830:/home/eljeffe# journalctl -xe|grep magicspam
Okt 09 08:15:01 h2729830.stratoserver.net CRON[7790]: pam_unix(cron:session): session opened for user magicspam by (uid=0)
Okt 09 08:15:01 h2729830.stratoserver.net CRON[7793]: (magicspam) CMD (find /etc/magicspam/db/queue -depth -mindepth 1 -maxdepth 1 -type f -cmin +5 -delete)
Okt 09 08:15:01 h2729830.stratoserver.net CRON[7790]: pam_unix(cron:session): session closed for user magicspam
Okt 09 08:18:33 h2729830.stratoserver.net magicspam-daemon[8252]: Starting magicspam-daemon .../usr/local/psa/admin/sbin/modules/magicspampro/magicspam-daemon: error while loading shared libraries: libdb-5.1.so: cannot open shared object file: No such file or directory
Okt 09 08:18:35 h2729830.stratoserver.net magicspam-daemon[8252]: Failed to start magicspam-daemon
Okt 09 08:19:09 h2729830.stratoserver.net magicspam-daemon[26815]: Starting magicspam-daemon .../usr/local/psa/admin/sbin/modules/magicspampro/magicspam-daemon: error while loading shared libraries: libdb-5.1.so: cannot open shared object file: No such file or directory
Okt 09 08:19:11 h2729830.stratoserver.net magicspam-daemon[26815]: Failed to start magicspam-daemon

System:

Code: Select all

root@h2729830:/home/eljeffe# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 16.04.3 LTS
Release:        16.04
Codename:       xenial

Plesk Onyx
Version 17.5.3 Update #24

[pheck]

I think, MagicSpam wants to use libdb-5.1 but I have libdb-5.3 installed. Version 5.1 is not available on my platform:

Code: Select all

root@h2729830:/home/eljeffe# dpkg -l|grep libdb
ii  libdb5.3:amd64                    5.3.28-11                              amd64        Berkeley v5.3 Database Libraries [runtime]
ii  libdbd-mysql-perl                 4.033-1ubuntu0.1                       amd64        Perl5 database interface to the MySQL database
ii  libdbi-perl                       1.634-1build1                          amd64        Perl Database Interface (DBI)
ii  libdbus-1-3:amd64                 1.10.6-1ubuntu3.3                      amd64        simple interprocess messaging system (library)
root@h2729830:/home/eljeffe# aptitude search libdb5
i   libdb5.3                                                                                      - Berkeley-Datenbank-Bibliotheken v5.3 [Laufzeit]
p   libdb5.3:i386                                                                                 - Berkeley-Datenbank-Bibliotheken v5.3 [Laufzeit]
p   libdb5.3++                                                                                    - C++-Berkeley-Datenbank-Bibliotheken v5.3 [Laufzeit]
p   libdb5.3++:i386                                                                               - C++-Berkeley-Datenbank-Bibliotheken v5.3 [Laufzeit]
p   libdb5.3++-dev                                                                                - C++-Berkeley-Datenbank-Bibliotheken v5.3 [Entwicklung]
p   libdb5.3++-dev:i386                                                                           - C++-Berkeley-Datenbank-Bibliotheken v5.3 [Entwicklung]
p   libdb5.3-dbg                                                                                  - Berkeley v5.3 Database Libraries [debug]
p   libdb5.3-dbg:i386                                                                             - Berkeley v5.3 Database Libraries [debug]
p   libdb5.3-dev                                                                                  - Berkeley-Datenbank-Bibliotheken v5.3 [Entwicklung]
p   libdb5.3-dev:i386                                                                             - Berkeley-Datenbank-Bibliotheken v5.3 [Entwicklung]
p   libdb5.3-java                                                                                 - Berkeley-Datenbank-Bibliotheken v5.3 für Java
v   libdb5.3-java:i386                                                                            -
p   libdb5.3-java-dev                                                                             - Java-Berkeley-Datenbank-Bibliotheken v5.3 [Entwicklung]
p   libdb5.3-java-dev:i386                                                                        - Java-Berkeley-Datenbank-Bibliotheken v5.3 [Entwicklung]
p   libdb5.3-java-gcj                                                                             - Berkeley v5.3 Database Libraries for Java (native code)
p   libdb5.3-java-gcj:i386                                                                        - Berkeley v5.3 Database Libraries for Java (native code)
p   libdb5.3-java-jni                                                                             - Berkeley-Datenbank-Bibliotheken v5.3 für Java
p   libdb5.3-java-jni:i386                                                                        - Berkeley-Datenbank-Bibliotheken v5.3 für Java
p   libdb5.3-sql                                                                                  - Berkeley-Datenbank-Bibliotheken v5.3 [SQL-Laufzeit]
p   libdb5.3-sql:i386                                                                             - Berkeley-Datenbank-Bibliotheken v5.3 [SQL-Laufzeit]
p   libdb5.3-sql-dev                                                                              - Berkeley-Datenbank-Bibliotheken v5.3 [SQL-Entwicklung]
p   libdb5.3-sql-dev:i386                                                                         - Berkeley-Datenbank-Bibliotheken v5.3 [SQL-Entwicklung]
p   libdb5.3-stl                                                                                  - Berkeley-Datenbank-Bibliotheken v5.3 [STL-Laufzeit]
p   libdb5.3-stl:i386                                                                             - Berkeley-Datenbank-Bibliotheken v5.3 [STL-Laufzeit]
p   libdb5.3-stl-dev                                                                              - Berkeley-Datenbank-Bibliotheken v5.3 [SQL-Entwicklung]
p   libdb5.3-stl-dev:i386                                                                         - Berkeley-Datenbank-Bibliotheken v5.3 [SQL-Entwicklung]
p   libdb5.3-tcl                                                                                  - Berkeley v5.3 Database Libraries for Tcl [module]
p   libdb5.3-tcl:i386                                                                             - Berkeley v5.3 Database Libraries for Tcl [module]

[pheck]

I have now reinstalled the MagicSpam Package and it looks, like this solved the issue.

Cheers Peter

[magicspam]

Hello Peter,

Thank you for the extensive logs and for updating us on this issue.

We are happy to hear that the issue was resolved after reinstalling MagicSpam in your system.

Please let us know if you have any other questions and have a great day!

[tkalfaoglu]

I had the same error in my logs.. In my case, the daemon was not working.. I started it manually... How can I ensure that this does not happen?

[magicspam]

Hello tkalfaoglu,

Thank you for letting us know.

We have now passed this information to our development team to create the mechanism to check if the service is running to prevent such issues in the future.

Thank you again to all who reported this issue.