1 Topic by morethanlazy (edited by morethanlazy 2019-06-09 23:49:49)

  • morethanlazy
  • Member
  • Offline
  • Registered: 2019-01-20
  • Posts: 38

Topic: Cron daily job failed message

==== REQUIRED BASIC INFO OF YOUR IREDMAIL SERVER ====
- iRedMail version (check /etc/iredmail-release): 0.9.9
- Deployed with iRedMail Easy or the downloadable installer? Downloaded
- Linux/BSD distribution name and version: ubuntu 18.04.2
- Store mail accounts in which backend (LDAP/MySQL/PGSQL): pgsql
- Web server (Apache or Nginx): nginx
- Manage mail accounts with iRedAdmin-Pro? No
- [IMPORTANT] Related original log or error message is required if you're experiencing an issue.
====
Good day, i got cron mail which indicates something went wrong and totally different than earlier cron mails i got.

Mail subject exactly this

Cron <root@mail> test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

And the message :

/etc/cron.daily/logrotate:
Job for rsyslog.service failed.
See "systemctl status rsyslog.service" and "journalctl -xe" for details.
error: error running non-shared postrotate script for /var/log/php-fpm/php-fpm.log of '/var/log/php-fpm/*.log '
run-parts: /etc/cron.daily/logrotate exited with return code 1

----

Spider Email Archiver: On-Premises, lightweight email archiving software developed by iRedMail team. Supports Amazon S3 compatible storage and custom branding.

2 Reply by morethanlazy (edited by morethanlazy 2019-06-09 23:55:00)

  • morethanlazy
  • Member
  • Offline
  • Registered: 2019-01-20
  • Posts: 38

Re: Cron daily job failed message

i run the commands again and here is the results :

root@mail:~# systemctl status rsyslog.service

● rsyslog.service - System Logging Service
   Loaded: loaded (/lib/systemd/system/rsyslog.service; enabled; vendor preset: enabled)
   Active: active (running) since Sun 2019-06-09 16:34:33 CEST; 1h 8min ago
     Docs: man:rsyslogd(8)
           http://www.rsyslog.com/doc/
Main PID: 1115 (rsyslogd)
    Tasks: 4 (limit: 2299)
   CGroup: /system.slice/rsyslog.service
           └─1115 /usr/sbin/rsyslogd -n

Jun 09 16:34:32 mail.gencmehmetoglu.engineer systemd[1]: Starting System Logging Service...
Jun 09 16:34:33 mail.gencmehmetoglu.engineer rsyslogd[1115]: imuxsock: Acquired UNIX socket '/run/systemd/journal/syslog' (fd 3) from systemd.  [v8.32.0]
Jun 09 16:34:33 mail.gencmehmetoglu.engineer rsyslogd[1115]: rsyslogd's groupid changed to 106
Jun 09 16:34:33 mail.gencmehmetoglu.engineer rsyslogd[1115]: rsyslogd's userid changed to 102
Jun 09 16:34:33 mail.gencmehmetoglu.engineer rsyslogd[1115]:  [origin software="rsyslogd" swVersion="8.32.0" x-pid="1115" x-info="http://www.rsyslog.com"] start
Jun 09 16:34:33 mail.gencmehmetoglu.engineer systemd[1]: Started System Logging Service.

root@mail:~# journalctl -xe

-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jun 09 17:42:58 mail.gencmehmetoglu.engineer systemd[1]: Started User Manager for UID 1000.
-- Subject: Unit user@1000.service has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit user@1000.service has finished starting up.
--
-- The start-up result is RESULT.
Jun 09 17:42:58 mail.gencmehmetoglu.engineer systemd[17279]: Reached target Default.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Jun 09 17:42:58 mail.gencmehmetoglu.engineer systemd[17279]: Startup finished in 83ms.
-- Subject: User manager start-up is now complete
-- Defined-By: systemd
-- Support: http://www.ubuntu.com/support
--
-- The user manager instance for user 1000 has been started. All services queued
-- for starting have been started. Note that other services might still be starting
-- up or be started at any later time.
--
-- Startup of the manager took 83284 microseconds.
Jun 09 17:43:08 mail.gencmehmetoglu.engineer sudo[17392]:     xxxx: TTY=pts/0 ; PWD=/home/xxxx; USER=root ; COMMAND=/bin/su -
Jun 09 17:43:08 mail.gencmehmetoglu.engineer sudo[17392]: pam_unix(sudo:session): session opened for user root by xxxx(uid=0)
Jun 09 17:43:08 mail.gencmehmetoglu.engineer su[17393]: Successful su for root by root
Jun 09 17:43:08 mail.gencmehmetoglu.engineer su[17393]: + /dev/pts/0 root:root
Jun 09 17:43:08 mail.gencmehmetoglu.engineer su[17393]: pam_unix(su:session): session opened for user root by xxxx(uid=0)
Jun 09 17:43:08 mail.gencmehmetoglu.engineer su[17393]: pam_systemd(su:session): Cannot create session: Already running in a session
Jun 09 17:43:15 mail.gencmehmetoglu.engineer dovecot[1268]: imap-login: Login: user=<postmaster@gencmehmetoglu.engineer>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=17410, secured, se
Jun 09 17:43:15 mail.gencmehmetoglu.engineer dovecot[1268]: imap(postmaster@gencmehmetoglu.engineer): Logged out in=389 out=2091
Jun 09 17:43:40 mail.gencmehmetoglu.engineer dovecot[1268]: imap-login: Login: user=<postmaster@gencmehmetoglu.engineer>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=17418, secured, se
Jun 09 17:43:40 mail.gencmehmetoglu.engineer dovecot[1268]: imap(postmaster@gencmehmetoglu.engineer): Logged out in=347 out=3746
Jun 09 17:44:41 mail.gencmehmetoglu.engineer dovecot[1268]: imap-login: Login: user=<postmaster@gencmehmetoglu.engineer>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=17428, secured, se
Jun 09 17:44:41 mail.gencmehmetoglu.engineer dovecot[1268]: imap(postmaster@gencmehmetoglu.engineer): Logged out in=347 out=3746
Jun 09 17:45:42 mail.gencmehmetoglu.engineer dovecot[1268]: imap-login: Login: user=<postmaster@gencmehmetoglu.engineer>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, mpid=17442, secured, se
Jun 09 17:45:42 mail.gencmehmetoglu.engineer dovecot[1268]: imap(postmaster@gencmehmetoglu.engineer): Logged out in=347 out=3746
Jun 09 17:45:42 mail.gencmehmetoglu.engineer php-fpm[1108]: [NOTICE] [pool inet] child 16927 exited with code 0 after 1414.462683 seconds from start
Jun 09 17:45:42 mail.gencmehmetoglu.engineer php-fpm[1108]: [NOTICE] [pool inet] child 17443 started
lines 1332-1380/1380 (END)

3 Reply by morethanlazy

  • morethanlazy
  • Member
  • Offline
  • Registered: 2019-01-20
  • Posts: 38

Re: Cron daily job failed message

and i run this command

test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily )

just Log watch mail received, cron mail hasnt been received

4 Reply by morethanlazy

  • morethanlazy
  • Member
  • Offline
  • Registered: 2019-01-20
  • Posts: 38

Re: Cron daily job failed message

Today all seems ok,


Message navigationMessage 2 of 259 Previous Next
Subject: Cron <root@mail> /bin/bash /var/vmail/backup/backup_pgsql.sh
From    root@mail.gencmehmetoglu.engineerAdd contact
To    root@mail.gencmehmetoglu.engineerAdd contact
Date    Today 04:01
Contact photo
Message Body

[OK] Backup successfully completed.

INSERT 0 1
* Backup log: /var/vmail/backup/pgsql/2019/06/10/2019-06-10-03-01-01.log:
* Starting at: 2019-06-10-03-01-01.
* Backup directory: /var/vmail/backup/pgsql/2019/06/10.
* Backing up databases: vmail roundcubemail amavisd iredadmin sogo iredapd.
  + vmail [DONE]
  + roundcubemail [DONE]
  + amavisd [DONE]
  + iredadmin [DONE]
  + iredapd [DONE]
* File size:
----
8.0K    amavisd-2019-06-10-03-01-01.sql.bz2
8.0K    iredadmin-2019-06-10-03-01-01.sql.bz2
12K    iredapd-2019-06-10-03-01-01.sql.bz2
8.0K    roundcubemail-2019-06-10-03-01-01.sql.bz2
8.0K    vmail-2019-06-10-03-01-01.sql.bz2
----
* Backup completed (Success? YES).
* Old backup found. Deleting: /var/vmail/backup/pgsql/2019/03/12.

5 Reply by morethanlazy

  • morethanlazy
  • Member
  • Offline
  • Registered: 2019-01-20
  • Posts: 38

Re: Cron daily job failed message

Right now all seems ok after restart the service. Solved by itself.