Skip to content
View in the app

A better way to browse. Learn more.
Froxlor Forum

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Apache2 startet nicht - libnss-mysql vor mysql ?

FlorianScholz
in German / Deutsch

Featured Replies

Hallihallo,

habe neuerdings folgendes Problem beim Reboot:

Apache2 startet nicht automatisch und beim Cronjob gibts den Fehler, dass ein froxloruser noch nicht existiert.

 

Log

Jul  3 21:59:01 srv01 Tine 2.0 scheduler: Tine 2.0 scheduler run (Tinebase_Alarm) complete.
Jul  3 21:59:47 srv01 dovecot: imap(webmaster@DOMAIN.net): Disconnected: Logged out in=621 out=5179
Jul  3 22:00:00 srv01 mysqld: 140703 22:00:00 [Note] /usr/sbin/mysqld: Normal shutdown
Jul  3 22:00:00 srv01 mysqld:
Jul  3 22:00:00 srv01 mysqld: 140703 22:00:00 [Note] Event Scheduler: Purging the queue. 0 events
Jul  3 22:00:00 srv01 mysqld: 140703 22:00:00  InnoDB: Starting shutdown...
Jul  3 22:00:01 srv01 /USR/SBIN/CRON[22845]: (root) CMD (/bin/chown -R tine:tine /usr/share/tine20)
Jul  3 22:00:01 srv01 CRON[22845]: libnss-mysql: Connection to server '127.0.0.1' failed: Can't connect to MySQL server on '127.0.0.1' (111)
Jul  3 22:00:01 srv01 /USR/SBIN/CRON[22846]: (root) CMD (/usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --tasks 1> /dev/null)
Jul  3 22:00:01 srv01 CRON[22843]: libnss-mysql: Connection to server '127.0.0.1' failed: Can't connect to MySQL server on '127.0.0.1' (111)
Jul  3 22:00:01 srv01 CRON[22843]: Fehler bei Authentifizierung
Jul  3 22:00:01 srv01 CRON[22846]: libnss-mysql: Connection to server '127.0.0.1' failed: Can't connect to MySQL server on '127.0.0.1' (111)
Jul  3 22:00:01 srv01 chown: libnss-mysql: Connection to server '127.0.0.1' failed: Can't connect to MySQL server on '127.0.0.1' (111)
Jul  3 22:00:01 srv01 CRON[22852]: libnss-mysql: Connection to server '127.0.0.1' failed: Can't connect to MySQL server on '127.0.0.1' (111)
Jul  3 22:00:01 srv01 postfix/cleanup[22856]: libnss-mysql: Connection to server '127.0.0.1' failed: Can't connect to MySQL server on '127.0.0.1' (111)
Jul  3 22:00:01 srv01 postfix/pickup[21885]: 5606D80682: uid=0 from=<root>
Jul  3 22:00:01 srv01 postfix/trivial-rewrite[22858]: libnss-mysql: Connection to server '127.0.0.1' failed: Can't connect to MySQL server on '127.0.0.1' (111)
Jul  3 22:00:01 srv01 postfix/cleanup[22856]: warning: connect to Milter service inet:localhost:8891: Connection refused
Jul  3 22:00:01 srv01 postfix/cleanup[22856]: warning: connect to mysql server 127.0.0.1: Can't connect to MySQL server on '127.0.0.1' (111)
Jul  3 22:00:01 srv01 postfix/cleanup[22856]: warning: mysql:/etc/postfix/mysql-virtual_alias_maps.cf lookup error for "root@mail.srv01.DOMAIN.net"
Jul  3 22:00:01 srv01 postfix/cleanup[22856]: warning: 5606D80682: virtual_alias_maps map lookup problem for root@mail.srv01.DOMAIN.net -- deferring delivery
Jul  3 22:00:01 srv01 mysqld: 140703 22:00:01  InnoDB: Shutdown completed; log sequence number 84978381
Jul  3 22:00:01 srv01 mysqld: 140703 22:00:01 [Note] /usr/sbin/mysqld: Shutdown complete
Jul  3 22:00:01 srv01 mysqld:
Jul  3 22:00:01 srv01 mysqld_safe: mysqld from pid file /var/run/mysqld/mysqld.pid ended
Jul  3 22:00:04 srv01 dovecot: master: Warning: Killed with signal 15 (by pid=22921 uid=0 code=kill)
Jul  3 22:00:04 srv01 dovecot: anvil: Warning: Killed with signal 15 (by pid=22921 uid=0 code=kill)
Jul  3 22:00:04 srv01 dovecot: log: Warning: Killed with signal 15 (by pid=22921 uid=0 code=kill)
Jul  3 22:00:04 srv01 postfix/master[2596]: terminating on signal 15
Jul  3 22:00:45 srv01 kernel: imklog 5.8.11, log source = /proc/kmsg started.
Jul  3 22:00:45 srv01 rsyslogd: [origin software="rsyslogd" swVersion="5.8.11" x-pid="1714" x-info="http://www.rsyslog.com"] start
Jul  3 22:00:46 srv01 mysqld_safe: Starting mysqld daemon with databases from /var/lib/mysql
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 [Warning] Using unique option prefix key_buffer instead of key_buffer_size is deprecated and will be removed in a future release. Please use the full name instead.
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 [Warning] Using unique option prefix myisam-recover instead of myisam-recover-options is deprecated and will be removed in a future release. Please use the full name instead.
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 [Note] Plugin 'FEDERATED' is disabled.
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 InnoDB: The InnoDB memory heap is disabled
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 InnoDB: Mutexes and rw_locks use GCC atomic builtins
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 InnoDB: Compressed tables use zlib 1.2.7
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 InnoDB: Using Linux native AIO
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 InnoDB: Initializing buffer pool, size = 128.0M
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 InnoDB: Completed initialization of buffer pool
Jul  3 22:00:46 srv01 mysqld: 140703 22:00:46 InnoDB: highest supported file format is Barracuda.
Jul  3 22:00:47 srv01 mysqld: 140703 22:00:47  InnoDB: Waiting for the background threads to start
Jul  3 22:00:48 srv01 mysqld: 140703 22:00:48 InnoDB: 5.5.37 started; log sequence number 84978381
Jul  3 22:00:48 srv01 mysqld: 140703 22:00:48 [Note] Server hostname (bind-address): '127.0.0.1'; port: 3306
Jul  3 22:00:48 srv01 mysqld: 140703 22:00:48 [Note]   - '127.0.0.1' resolves to '127.0.0.1';
Jul  3 22:00:48 srv01 mysqld: 140703 22:00:48 [Note] Server socket created on IP: '127.0.0.1'.
Jul  3 22:00:48 srv01 mysqld: 140703 22:00:48 [Note] Event Scheduler: Loaded 0 events
Jul  3 22:00:48 srv01 mysqld: 140703 22:00:48 [Note] /usr/sbin/mysqld: ready for connections.
Jul  3 22:00:48 srv01 mysqld: Version: '5.5.37-0+wheezy1'  socket: '/var/run/mysqld/mysqld.sock'  port: 3306  (Debian)
Jul  3 22:00:48 srv01 /etc/mysql/debian-start[2191]: Upgrading MySQL tables if necessary.
Jul  3 22:00:49 srv01 /etc/mysql/debian-start[2195]: /usr/bin/mysql_upgrade: the '--basedir' option is always ignored
Jul  3 22:00:49 srv01 /etc/mysql/debian-start[2195]: Looking for 'mysql' as: /usr/bin/mysql
Jul  3 22:00:49 srv01 /etc/mysql/debian-start[2195]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck
Jul  3 22:00:49 srv01 /etc/mysql/debian-start[2195]: This installation of MySQL is already upgraded to 5.5.37, use --force if you still need to run mysql_upgrade
Jul  3 22:00:49 srv01 /etc/mysql/debian-start[2257]: Checking for insecure root accounts.
Jul  3 22:00:49 srv01 /etc/mysql/debian-start[2262]: Triggering myisam-recover for all MyISAM tables
Jul  3 22:00:49 srv01 /usr/sbin/cron[2308]: (CRON) INFO (pidfile fd = 3)
Jul  3 22:00:49 srv01 /usr/sbin/cron[2309]: (CRON) STARTUP (fork ok)
Jul  3 22:00:49 srv01 /usr/sbin/cron[2309]: (CRON) INFO (Running @reboot jobs)
Jul  3 22:00:54 srv01 dovecot: master: Dovecot v2.1.7 starting up
Jul  3 22:00:56 srv01 postfix/master[2638]: daemon started -- version 2.9.6, configuration /etc/postfix
Jul  3 22:00:57 srv01 postfix/pickup[2660]: 22BD880790: uid=0 from=<root>
Jul  3 22:00:57 srv01 postfix/cleanup[2668]: warning: connect to Milter service inet:localhost:8891: Connection refused
Jul  3 22:00:57 srv01 postfix/cleanup[2668]: 22BD880790: message-id=<20140703200057.22BD880790@mail.srv01.DOMAIN.net>
Jul  3 22:00:58 srv01 postfix/qmgr[2661]: 22BD880790: from=<root@mail.srv01.DOMAIN.net>, size=643, nrcpt=1 (queue active)
Jul  3 22:00:58 srv01 postfix/cleanup[2668]: 2B69C80684: message-id=<20140703200057.22BD880790@mail.srv01.DOMAIN.net>
Jul  3 22:00:58 srv01 postfix/qmgr[2661]: 2B69C80684: from=<root@mail.srv01.DOMAIN.net>, size=789, nrcpt=1 (queue active)
Jul  3 22:00:58 srv01 postfix/local[2700]: 22BD880790: to=<root@mail.srv01.DOMAIN.net>, orig_to=<root>, relay=local, delay=57, delays=57/0.09/0/0.08, dsn=2.0.0, status=sent (forwarded as 2B69C80684)
Jul  3 22:00:58 srv01 postfix/qmgr[2661]: 22BD880790: removed
Jul  3 22:00:58 srv01 dovecot: auth-worker(2705): mysql(127.0.0.1): Connected to database froxlor
Jul  3 22:00:58 srv01 dovecot: lda(webmaster@DOMAIN.net): msgid=<20140703200057.22BD880790@mail.srv01.DOMAIN.net>: saved mail to INBOX
Jul  3 22:00:58 srv01 postfix/pipe[2701]: 2B69C80684: to=<webmaster@DOMAIN.net>, orig_to=<root>, relay=dovecot, delay=0.75, delays=0.05/0.03/0/0.67, dsn=2.0.0, status=sent (delivered via dovecot service)
Jul  3 22:00:58 srv01 postfix/qmgr[2661]: 2B69C80684: removed
Jul  3 22:01:01 srv01 /USR/SBIN/CRON[2713]: (root) CMD (/bin/chown -R tine:tine /usr/share/tine20)
Jul  3 22:01:01 srv01 /USR/SBIN/CRON[2714]: (tine) CMD (/usr/bin/php -f /usr/share/tine20/tine20.php -- --config=/usr/share/tine20/config.inc.php --method=Tinebase.triggerAsyncEvents | logger -p daemon.notice -t "Tine 2.0 scheduler")
Jul  3 22:01:07 srv01 Tine 2.0 scheduler: Tine 2.0 scheduler run (Tinebase_Alarm) complete.
Jul  3 22:02:01 srv01 /USR/SBIN/CRON[2829]: (root) CMD (/bin/chown -R tine:tine /usr/share/tine20)
Jul  3 22:02:01 srv01 /USR/SBIN/CRON[2830]: (root) CMD (/usr/bin/nice -n 5 /usr/bin/php5 -q /var/www/froxlor/scripts/froxlor_master_cronjob.php --tasks 1> /dev/null)
Jul  3 22:02:01 srv01 /USR/SBIN/CRON[2833]: (tine) CMD (/usr/bin/php -f /usr/share/tine20/tine20.php -- --config=/usr/share/tine20/config.inc.php --method=Tinebase.triggerAsyncEvents | logger -p daemon.notice -t "Tine 2.0 scheduler")
Jul  3 22:02:01 srv01 Tine 2.0 scheduler: Tine 2.0 scheduler run (Tinebase_Alarm) complete.

Ich nehme an, dass mysql zu sp?t startet und deshalb libnss-mysql noch nicht auf mysql zugreifen kann. Jmd ein ?hnliches Problem gehabt? Jmd eine Idee, wie ich das beheben kann?

 

Beste Gr??e,

Florian

Du kannst die Startskripte in /etc/rc3.d/ umbennen, die werden von SysVinit alphabetisch abgearbeitet, falls du ein System hast welches noch kein Upstart oder Systemd benutzt, da hab ich keine Ahnung von. Die Skripte sind normalerweise eh schon nummeriert, da brauchst du nur die Nummer von Apache etc. erh?hen, dass er nach MySQL startet.

Archived

This topic is now archived and is closed to further replies.

Go to topic listing

Account

Navigation

Search

Search

Configure browser push notifications
Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.