Autoshutdown funktioniert nicht

tauchvogel · 15. Februar 2021

Bei mir funktioniert Autoshutdown nicht. Der PC geht nicht in den Ruhezustand.

Hier ein Auszug der Logdatei:

Code

b 15 14:12:22 debian-nas autoshutdown[3353]: root: INFO: 'main(): Sleep for 180s'
Feb 15 14:15:22 debian-nas autoshutdown[3353]: root: INFO: 'main(): ------------------------------------------------------'
Feb 15 14:15:22 debian-nas autoshutdown[3353]: root: INFO: 'main(): New supervision cycle started, checking system activity'
Feb 15 14:15:23 debian-nas autoshutdown[3353]: root: INFO: '_ping_range(): Retrieve list of active IPs for: enp3s0'
Feb 15 14:15:24 debian-nas autoshutdown[3353]: root: INFO: '_ping_range(): No active IPs found in the specified range -> next check'
Feb 15 14:15:24 debian-nas autoshutdown[3353]: root: INFO: '_check_net_status(): Check connections for: enp3s0'
Feb 15 14:15:24 debian-nas autoshutdown[3353]: root: INFO: '_check_net_status(): Found 0 active socket(s) on enp3s0, from port(s): 3689,6991,9091,49152'
Feb 15 14:15:24 debian-nas autoshutdown[3353]: root: INFO: '_check_docker_status(): Found 0 active socket(s), from port(s): 3689,6991,9091,49152'
Feb 15 14:15:24 debian-nas autoshutdown[3353]: root: INFO: '_check_users_cli_status(): There are no users connected -> next check'
Feb 15 14:15:24 debian-nas autoshutdown[3353]: root: INFO: '_check_ul_dl_rate(): Running on interface: enp3s0'
Feb 15 14:15:24 debian-nas autoshutdown[3353]: root: INFO: '_check_ul_dl_rate(): Network interface: enp3s0 (last 187s) DL: 1.3 kB/s, UL: 0.1 kB/s under 50 kB/s -> next check'
Feb 15 14:15:24 debian-nas autoshutdown[3353]: root: INFO: '_check_hddio(): Device: sdb (last 187s) kB_read/s: 23.2, kB_wrtn/s: 3456.0 over: 401 kB/s -> no shutdown'
Feb 15 14:15:24 debian-nas autoshutdown[3353]: root: INFO: '_check_hddio(): All checks complete'
Feb 15 14:15:25 debian-nas autoshutdown[3353]: root: INFO: 'main(): Sleep for 180s'
Feb 15 14:18:25 debian-nas autoshutdown[3353]: root: INFO: 'main(): ------------------------------------------------------'
Feb 15 14:18:25 debian-nas autoshutdown[3353]: root: INFO: 'main(): New supervision cycle started, checking system activity'
Feb 15 14:18:25 debian-nas autoshutdown[3353]: root: INFO: '_ping_range(): Retrieve list of active IPs for: enp3s0'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_ping_range(): No active IPs found in the specified range -> next check'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_check_net_status(): Check connections for: enp3s0'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_check_net_status(): Found 0 active socket(s) on enp3s0, from port(s): 3689,6991,9091,49152'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_check_docker_status(): Found 0 active socket(s), from port(s): 3689,6991,9091,49152'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_check_users_cli_status(): There are no users connected -> next check'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_check_ul_dl_rate(): Running on interface: enp3s0'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_check_ul_dl_rate(): Network interface: enp3s0 (last 182s) DL: 0.4 kB/s, UL: 0.1 kB/s under 50 kB/s -> next check'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_check_hddio(): Device: sdb (last 182s) kB_read/s: 0.0, kB_wrtn/s: 6.7 under: 401 kB/s -> next check'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_check_hddio(): Device: md127 (last 182s) kB_read/s: 0.0, kB_wrtn/s: 0.0 under: 401 kB/s -> next check'
Feb 15 14:18:26 debian-nas autoshutdown[3353]: root: INFO: '_check_hddio(): All checks complete'
Feb 15 14:18:31 debian-nas autoshutdown[3353]: root: INFO: '_check_processes(): Found 0 process(es) active -> next check'
Feb 15 14:18:32 debian-nas autoshutdown[3353]: root: INFO: 'main(): All active checks passed, 2 cycles until shutdown...'
Feb 15 14:18:32 debian-nas autoshutdown[3353]: root: INFO: 'main(): Sleep for 180s'
Feb 15 14:21:32 debian-nas autoshutdown[3353]: root: INFO: 'main(): ------------------------------------------------------'
Feb 15 14:21:32 debian-nas autoshutdown[3353]: root: INFO: 'main(): New supervision cycle started, checking system activity'
Feb 15 14:21:32 debian-nas autoshutdown[3353]: root: INFO: '_ping_range(): Retrieve list of active IPs for: enp3s0'
Feb 15 14:21:33 debian-nas autoshutdown[3353]: root: INFO: '_ping_range(): No active IPs found in the specified range -> next check'
Feb 15 14:21:33 debian-nas autoshutdown[3353]: root: INFO: '_check_net_status(): Check connections for: enp3s0'
Feb 15 14:21:33 debian-nas autoshutdown[3353]: root: INFO: '_check_net_status(): Found 0 active socket(s) on enp3s0, from port(s): 3689,6991,9091,49152'
Feb 15 14:21:33 debian-nas autoshutdown[3353]: root: INFO: '_check_docker_status(): Found 0 active socket(s), from port(s): 3689,6991,9091,49152'
Feb 15 14:21:33 debian-nas autoshutdown[3353]: root: INFO: '_check_users_cli_status(): There are no users connected -> next check'
Feb 15 14:21:33 debian-nas autoshutdown[3353]: root: INFO: '_check_ul_dl_rate(): Running on interface: enp3s0'
Feb 15 14:21:33 debian-nas autoshutdown[3353]: root: INFO: '_check_ul_dl_rate(): Network interface: enp3s0 (last 187s) DL: 0.8 kB/s, UL: 0.2 kB/s under 50 kB/s -> next check'
Feb 15 14:21:33 debian-nas autoshutdown[3353]: root: INFO: '_check_hddio(): Device: sdb (last 187s) kB_read/s: 0.0, kB_wrtn/s: 17.0 under: 401 kB/s -> next check'
Feb 15 14:21:34 debian-nas autoshutdown[3353]: root: INFO: '_check_hddio(): Device: md127 (last 187s) kB_read/s: 0.0, kB_wrtn/s: 0.0 under: 401 kB/s -> next check'
Feb 15 14:21:34 debian-nas autoshutdown[3353]: root: INFO: '_check_hddio(): All checks complete'
Feb 15 14:21:39 debian-nas autoshutdown[3353]: root: INFO: '_check_processes(): Found 0 process(es) active -> next check'

Alles anzeigen

Was kann ich tun?

wtuppa · 15. Februar 2021

Code

'main(): All active checks passed, 2 cycles until shutdown...'

im mittleren Log, d.h. es war wohl noch etwas Zeit notwendig (du hast nur einen weiteren Shutdown Log...). Die Anzahl der Checks kannst du in der GUI einstellen.

tauchvogel · 18. Februar 2021

Warum ist da eine rote "Leuchte"?

Hier mal ein Syslog-Auszug des Plugins:

Code

Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_config(): Checking config: /etc/autoshutdown.conf'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: WARNING: '_check_config(): CHECKCLOCKACTIVE set false not validating UPHOURS and OVERRIDEUPHOURS'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_config(): Kernel 5.10.0-0.bpo.3-amd64 supports power management modes:'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_config(): Kernel supports: HIBERNATE (suspend to DISK)'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_config(): Kernel supports: HYBRID (suspend to RAM and DISK)'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_config(): Kernel supports: SUSPEND (suspend to RAM)'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_config(): SHUTDOWNCOMMAND is set to: systemctl hibernate'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_networkconfig(): ------------------------------------------------------'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_networkconfig(): Find available network interfaces and their IPv4 addresses'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_networkconfig(): 'enp3s0' has IPv4 address: 192.168.178.39'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: 'main(): --------------- Initialise states --------------------'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_hddio(): All checks complete'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: '_check_ul_dl_rate(): Running on interface: enp3s0'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: 'main(): ---------------- Script started ----------------------'
Feb 17 15:49:22 debian-nas autoshutdown[711]: root: INFO: 'main(): Waiting 5 minutes until the first check'
Feb 17 15:50:04 debian-nas autoshutdown[2003]: : INFO: 'autoshutdown-restart(): Autoshutdown stopping'
Feb 17 15:50:11 debian-nas autoshutdown[2049]: : INFO: 'autoshutdown-restart(): Autoshutdown starting'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: 'main(): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: 'main(): Openmediavault-autoshutdown version: 5.1.10'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: 'main(): Script md5sum: 797d77704d47042f9c89017df30894f2'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: 'main(): /etc/autoshutdown.conf loaded'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: 'main(): /etc/autoshutdown.default loaded'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: '_check_config(): ------------------------------------------------------'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: '_check_config(): Checking config: /etc/autoshutdown.conf'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: WARNING: '_check_config(): CHECKCLOCKACTIVE set false not validating UPHOURS and OVERRIDEUPHOURS'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: '_check_config(): Kernel 5.10.0-0.bpo.3-amd64 supports power management modes:'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: '_check_config(): Kernel supports: HIBERNATE (suspend to DISK)'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: '_check_config(): Kernel supports: HYBRID (suspend to RAM and DISK)'
Feb 17 15:50:11 debian-nas autoshutdown[2191]: root: INFO: '_check_config(): Kernel supports: SUSPEND (suspend to RAM)'
Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: '_check_config(): SHUTDOWNCOMMAND is set to: systemctl hibernate'
Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: '_check_networkconfig(): ------------------------------------------------------'
Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: '_check_networkconfig(): Find available network interfaces and their IPv4 addresses'
Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: '_check_networkconfig(): 'enp3s0' has IPv4 address: 192.168.178.39'
Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: 'main(): --------------- Initialise states --------------------'
Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: '_check_hddio(): All checks complete'
Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: '_check_ul_dl_rate(): Running on interface: enp3s0'
Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: 'main(): ---------------- Script started ----------------------'
Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: 'main(): Waiting 5 minutes until the first check'
Feb 17 15:51:19 debian-nas autoshutdown[2687]: : INFO: 'autoshutdown-restart(): Autoshutdown stopping'
Feb 18 20:49:26 debian-nas autoshutdown[2747]: : INFO: 'autoshutdown-restart(): Autoshutdown starting'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: INFO: 'main(): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: INFO: 'main(): Openmediavault-autoshutdown version: 5.1.10'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: INFO: 'main(): Script md5sum: 797d77704d47042f9c89017df30894f2'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: INFO: 'main(): /etc/autoshutdown.conf loaded'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: INFO: 'main(): /etc/autoshutdown.default loaded'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: INFO: '_check_config(): ------------------------------------------------------'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: INFO: '_check_config(): Checking config: /etc/autoshutdown.conf'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: WARNING: '_check_config(): CHECKCLOCKACTIVE set false not validating UPHOURS and OVERRIDEUPHOURS'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: INFO: '_check_config(): Kernel 5.10.0-0.bpo.3-amd64 supports power management modes:'
Feb 18 20:49:26 debian-nas autoshutdown[3033]: root: INFO: '_check_config(): Kernel supports: HIBERNATE (suspend to DISK)'
Feb 18 20:49:27 debian-nas autoshutdown[3033]: root: INFO: '_check_config(): Kernel supports: HYBRID (suspend to RAM and DISK)'
Feb 18 20:49:27 debian-nas autoshutdown[3033]: root: INFO: '_check_config(): Kernel supports: SUSPEND (suspend to RAM)'
Feb 18 20:49:27 debian-nas autoshutdown[3033]: root: INFO: '_check_config(): SHUTDOWNCOMMAND is set to: systemctl hibernate'
Feb 18 20:49:27 debian-nas autoshutdown[3033]: root: INFO: '_check_networkconfig(): ------------------------------------------------------'
Feb 18 20:49:27 debian-nas autoshutdown[3033]: root: INFO: '_check_networkconfig(): Find available network interfaces and their IPv4 addresses'
Feb 18 20:49:27 debian-nas autoshutdown[3033]: root: ERR: '_check_networkconfig(): No valid network interface found, exiting ...'

Alles anzeigen

tauchvogel · 18. Februar 2021

Und hier mal ein Syslog-Auszug:Feb 18 21:13:08 debian-nas cron-apt: Get:2 https://dl.bintray.com/openmediavault-plugin-developers/usul buster/main amd64 openmediavault-autoshutdown all 5.1.11 [48.1 kB]

Code

Feb 18 21:13:08 debian-nas postfix/qmgr[1068]: ABF601603C7: from=<jjj>, size=4817, nrcpt=2 (queue active)
Feb 18 21:13:08 debian-nas postfix/pipe[4964]: ABF601603C7: to=<openmediavault-notification@localhost.localdomain>, relay=omvnotificationfilter, delay=0.11, delays=0.07/0.02/0/0.03, dsn=2.0.0, status=sent (delivered via omvnotificationfilter service)
Feb 18 21:13:08 debian-nas anacron[2721]: Job `cron.daily' terminated
Feb 18 21:13:08 debian-nas anacron[2721]: Normal exit (1 job run)
Feb 18 21:13:08 debian-nas systemd[1]: anacron.service: Succeeded.
Feb 18 21:13:09 debian-nas postfix/smtp[4965]: ABF601603C7: replace: header Subject: CRON-APT completed on debian-nas [/etc/cron-apt/con: Subject: [debian-nas] CRON-APT completed on debian-nas [/etc/cron-apt/config]
Feb 18 21:13:09 debian-nas postfix/smtp[4965]: ABF601603C7: to=<kkkkk>, relay=smtp.web.de[213.165.67.108]:587, delay=0.87, delays=0.07/0.07/0.65/0.09, dsn=2.0.0, status=sent (250 Requested mail action okay, completed: id=1MDv9M-1l2yJW1h24-009zAY)
Feb 18 21:13:09 debian-nas postfix/qmgr[1068]: ABF601603C7: removed
Feb 18 21:15:01 debian-nas CRON[5007]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 18 21:15:01 debian-nas CRON[5008]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)
Feb 18 21:16:08 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:16:41 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:16:51 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:17:01 debian-nas CRON[5285]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)
Feb 18 21:17:02 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:17:14 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:17:24 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:17:34 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:17:45 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:17:46 debian-nas smartd[521]: Device: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3CUHJN4 [SAT], SMART Prefailure Attribute: 3 Spin_Up_Time changed from 180 to 181
Feb 18 21:17:46 debian-nas smartd[521]: Device: /dev/disk/by-id/ata-WDC_WD30EFRX-68EUZN0_WD-WCC4N3CUHKK9 [SAT], SMART Prefailure Attribute: 3 Spin_Up_Time changed from 181 to 180
Feb 18 21:17:55 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:18:06 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:18:18 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:18:28 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:18:38 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:18:49 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:18:59 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:19:09 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:19:22 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:19:32 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:19:42 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:19:52 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:20:02 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:20:12 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:20:24 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:20:34 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:20:44 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.
Feb 18 21:20:53 debian-nas systemd[1]: /lib/systemd/system/fail2ban.service:12: PIDFile= references path below legacy directory /var/run/, updating /var/run/fail2ban/fail2ban.pid → /run/fail2ban/fail2ban.pid; please update the unit file accordingly.

Alles anzeigen

wtuppa · 19. Februar 2021

Zitat von tauchvogel

Feb 17 15:50:12 debian-nas autoshutdown[2191]: root: INFO: '_check_networkconfig(): 'enp3s0' has IPv4 address: 192.168.178.39'

Feb 18 20:49:27 debian-nas autoshutdown[3033]: root: ERR: '_check_networkconfig(): No valid network interface found, exiting ...'

irgendwie passiert da was mit deiner Netzwerkkarte. Zuerst hat er sie erkannt und alles ging gut, und dann beim (anscheinend nächsten Boot) steigt er aus, da er keine Netzwerkkarte findet. Keine Ahnung, was da passiert. Aber definitiv deshalb die rote Leuchte.

tauchvogel · 21. Februar 2021

Zitat von wtuppa

irgendwie passiert da was mit deiner Netzwerkkarte. Zuerst hat er sie erkannt und alles ging gut, und dann beim (anscheinend nächsten Boot) steigt er aus, da er keine Netzwerkkarte findet. Keine Ahnung, was da passiert. Aber definitiv deshalb die rote Leuchte.

Das kann sein, weiss ich aber derzeit nicht.

Nun, ich habe weiter gestestet und Autoshutdown funktioniert immernoch nicht.

Im Log des Autoshutdown, steht etwas, dass er immer wieder IPs findet, die das System wach halten: Keine Ahnung welche IPs das sein sollen.

Code

eb 21 21:58:01 debian-nas autoshutdown[25038]: root: INFO: 'main(): ------------------------------------------------------'
Feb 21 21:58:01 debian-nas autoshutdown[25038]: root: INFO: 'main(): New supervision cycle started, checking system activity'
Feb 21 21:58:01 debian-nas autoshutdown[25038]: root: INFO: '_ping_range(): Retrieve list of active IPs for: enp3s0'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_ping_range(): No active IPs found in the specified range -> next check'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_check_net_status(): Check connections for: enp3s0'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_check_net_status(): Found 0 active socket(s) on enp3s0, from port(s): 80'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_check_docker_status(): Found 0 active socket(s), from port(s): 80'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_check_ul_dl_rate(): Running on interface: enp3s0'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_check_ul_dl_rate(): Network interface: enp3s0 (last 67s) DL: 0.5 kB/s, UL: 0.0 kB/s under 1000 kB/s -> next check'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_check_hddio(): Device: sdb (last 67s) kB_read/s: 0.0, kB_wrtn/s: 6.6 under: 401 kB/s -> next check'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_check_hddio(): Device: md127 (last 67s) kB_read/s: 0.0, kB_wrtn/s: 0.0 under: 401 kB/s -> next check'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_check_hddio(): All checks complete'
Feb 21 21:58:03 debian-nas autoshutdown[25038]: root: INFO: '_check_smart(): No supported device is running SMART tests -> next check'
Feb 21 21:58:08 debian-nas autoshutdown[25038]: root: INFO: '_check_processes(): Found 0 process(es) active -> next check'
Feb 21 21:58:08 debian-nas autoshutdown[25038]: root: INFO: '_check_loadaverage(): Load average (0.08 -> 8) is lower than target (40) -> next check'
Feb 21 21:58:08 debian-nas autoshutdown[25038]: root: INFO: 'main(): All active checks passed, 0 cycles until shutdown...'
Feb 21 21:58:08 debian-nas autoshutdown[25038]: root: INFO: '_shutdown(): Shutdown issued: systemctl hibernate'
Feb 21 21:58:17 debian-nas autoshutdown[26074]: : INFO: 'autoshutdown-restart(): Autoshutdown starting'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: 'main(): XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: 'main(): Openmediavault-autoshutdown version: 5.1.11'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: 'main(): Script md5sum: d5187a8062fc70450c3cfc66dc2a47d9'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: 'main(): /etc/autoshutdown.default loaded'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: 'main(): /etc/autoshutdown.conf loaded'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_config(): ------------------------------------------------------'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_config(): Checking config: /etc/autoshutdown.conf'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: WARNING: '_check_config(): CHECKCLOCKACTIVE set false not validating UPHOURS and OVERRIDEUPHOURS'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_config(): Kernel 5.10.0-0.bpo.3-amd64 supports power management modes:'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_config(): Kernel supports: HIBERNATE (suspend to DISK)'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_config(): Kernel supports: SUSPEND (suspend to RAM)'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_config(): Kernel supports: HYBRID-SLEEP (suspend to RAM and DISK)'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_config(): SHUTDOWNCOMMAND is set to: systemctl hibernate'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_networkconfig(): ------------------------------------------------------'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_networkconfig(): Find available network interfaces and their IPv4 addresses'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_networkconfig(): 'enp3s0' has IPv4 address: 192.168.178.39'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: 'main(): --------------- Initialise states --------------------'
Feb 21 21:58:17 debian-nas autoshutdown[26229]: root: INFO: '_check_hddio(): All checks complete'
Feb 21 21:58:18 debian-nas autoshutdown[26229]: root: INFO: '_check_ul_dl_rate(): Running on interface: enp3s0'
Feb 21 21:58:18 debian-nas autoshutdown[26229]: root: INFO: 'main(): ---------------- Script started ----------------------'
Feb 21 21:58:18 debian-nas autoshutdown[26229]: root: INFO: 'main(): Waiting 5 minutes until the first check'

Alles anzeigen

Was hindert das System daran?

Hier Screenshots von den Autoshutdown Einstellungen:

Ich habe Portainer, dort Plex installiert. Außerdem laufen minidlna, fail2ban, antivir.

tauchvogel · 21. Februar 2021

Ich muss wegen der Zeichenlänge eine weitere Antwort erstellen.

Hier mal ein Auszug des LOG-Textes von Syslog:

Code

Feb 21 21:50:46 debian-nas systemd[1]: Stopped target Sleep.
Feb 21 21:50:46 debian-nas systemd[1]: Started openmediavault-autoshutdown plugin service.
Feb 21 21:53:27 debian-nas clamd[567]: Sun Feb 21 21:53:27 2021 -> SelfCheck: Database status OK.
Feb 21 21:55:01 debian-nas CRON[25272]: (root) CMD (command -v debian-sa1 > /dev/null && debian-sa1 1 1)
Feb 21 21:58:08 debian-nas systemd[1]: Reached target Sleep.
Feb 21 21:58:08 debian-nas systemd[1]: Starting Hibernate...
Feb 21 21:58:08 debian-nas systemd[1]: autoshutdown.service: Succeeded.
Feb 21 21:58:08 debian-nas kernel: [ 7512.048058] PM: Image not found (code -22)
Feb 21 21:58:08 debian-nas watchdog[24936]: stopping daemon (5.15)
Feb 21 21:58:08 debian-nas systemd[1]: Stopping watchdog daemon...
Feb 21 21:58:09 debian-nas systemd[1]: watchdog.service: Succeeded.
Feb 21 21:58:09 debian-nas systemd[1]: Stopped watchdog daemon.
Feb 21 21:58:09 debian-nas systemd-sleep[26025]: Suspending system...
Feb 21 21:58:09 debian-nas kernel: [ 7512.217533] PM: hibernation: hibernation entry
Feb 21 21:58:17 debian-nas kernel: [ 7512.219556] Filesystems sync: 0.001 seconds
Feb 21 21:58:17 debian-nas kernel: [ 7512.219561] Freezing user space processes ... (elapsed 0.001 seconds) done.
Feb 21 21:58:17 debian-nas kernel: [ 7512.221368] OOM killer disabled.
Feb 21 21:58:17 debian-nas kernel: [ 7512.221651] PM: hibernation: Marking nosave pages: [mem 0x0003e000-0x0003ffff]
Feb 21 21:58:17 debian-nas kernel: [ 7512.221656] PM: hibernation: Marking nosave pages: [mem 0x0009e000-0x000fffff]
Feb 21 21:58:17 debian-nas kernel: [ 7512.221661] PM: hibernation: Marking nosave pages: [mem 0x10000000-0x12150fff]
Feb 21 21:58:17 debian-nas kernel: [ 7512.221936] PM: hibernation: Marking nosave pages: [mem 0x69d0b000-0x69d0bfff]

Feb 21 21:58:17 debian-nas kernel: [ 7512.227273] PM: hibernation: Basic memory bitmaps created
Feb 21 21:58:17 debian-nas kernel: [ 7512.228176] PM: hibernation: Preallocating image memory
Feb 21 21:58:17 debian-nas kernel: [ 7513.288922] PM: hibernation: Allocated 757654 pages for snapshot
Feb 21 21:58:17 debian-nas kernel: [ 7513.288927] PM: hibernation: Allocated 3030616 kbytes in 1.06 seconds (2859.07 MB/s)
Feb 21 21:58:17 debian-nas kernel: [ 7513.288929] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done.
Feb 21 21:58:17 debian-nas kernel: [ 7513.290443] printk: Suspending console(s) (use no_console_suspend to debug)
Feb 21 21:58:17 debian-nas kernel: [ 7513.291017] serial 00:01: disabled
Feb 21 21:58:17 debian-nas kernel: [ 7513.291932] r8169 0000:03:00.0 enp3s0: Link is Down
Feb 21 21:58:17 debian-nas kernel: [ 7513.559795] ACPI: Preparing to enter system sleep state S4
Feb 21 21:58:17 debian-nas kernel: [ 7513.767424] PM: Saving platform NVS memory
Feb 21 21:58:17 debian-nas kernel: [ 7513.767684] Disabling non-boot CPUs ...
Feb 21 21:58:17 debian-nas kernel: [ 7513.769115] smpboot: CPU 1 is now offline
Feb 21 21:58:17 debian-nas kernel: [ 7513.771737] smpboot: CPU 2 is now offline
Feb 21 21:58:17 debian-nas kernel: [ 7513.774271] smpboot: CPU 3 is now offline
Feb 21 21:58:17 debian-nas kernel: [ 7513.776889] PM: hibernation: Creating image:
Feb 21 21:58:17 debian-nas kernel: [ 7513.920782] PM: hibernation: Need to copy 755973 pages
Feb 21 21:58:17 debian-nas kernel: [ 7513.920786] PM: hibernation: Normal pages needed: 755973 + 1024, available pages: 1250107
Feb 21 21:58:17 debian-nas kernel: [ 7514.748465] PM: hibernation: Image created (755973 pages copied)
Feb 21 21:58:17 debian-nas kernel: [ 7513.776996] PM: Restoring platform NVS memory
Feb 21 21:58:17 debian-nas kernel: [ 7513.777923] Enabling non-boot CPUs ...
Feb 21 21:58:17 debian-nas kernel: [ 7513.778023] x86: Booting SMP configuration:
Feb 21 21:58:17 debian-nas kernel: [ 7513.778024] smpboot: Booting Node 0 Processor 1 APIC 0x2
Feb 21 21:58:17 debian-nas kernel: [ 7513.779393] CPU1 is up
Feb 21 21:58:17 debian-nas kernel: [ 7513.779438] smpboot: Booting Node 0 Processor 2 APIC 0x4
Feb 21 21:58:17 debian-nas kernel: [ 7513.780697] CPU2 is up
Feb 21 21:58:17 debian-nas kernel: [ 7513.780741] smpboot: Booting Node 0 Processor 3 APIC 0x6
Feb 21 21:58:17 debian-nas kernel: [ 7513.782029] CPU3 is up
Feb 21 21:58:17 debian-nas kernel: [ 7513.782376] ACPI: Waking up from system sleep state S4
Feb 21 21:58:17 debian-nas kernel: [ 7513.828031] serial 00:01: activated
Feb 21 21:58:17 debian-nas kernel: [ 7513.949433] r8169 0000:03:00.0 enp3s0: Link is Down
Feb 21 21:58:17 debian-nas kernel: [ 7514.019319] acpi LNXPOWER:06: Turning OFF
Feb 21 21:58:17 debian-nas kernel: [ 7514.019374] acpi LNXPOWER:05: Turning OFF
Feb 21 21:58:17 debian-nas kernel: [ 7514.019427] acpi LNXPOWER:04: Turning OFF
Feb 21 21:58:17 debian-nas kernel: [ 7514.019480] acpi LNXPOWER:03: Turning OFF
Feb 21 21:58:17 debian-nas kernel: [ 7514.019532] acpi LNXPOWER:02: Turning OFF
Feb 21 21:58:17 debian-nas kernel: [ 7514.019583] acpi LNXPOWER:01: Turning OFF
Feb 21 21:58:17 debian-nas kernel: [ 7514.019636] acpi LNXPOWER:00: Turning OFF
Feb 21 21:58:17 debian-nas kernel: [ 7514.152682] ata2: SATA link down (SStatus 4 SControl 300)
Feb 21 21:58:17 debian-nas kernel: [ 7514.301425] ata3: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 21 21:58:17 debian-nas kernel: [ 7514.301463] ata4: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 21 21:58:17 debian-nas kernel: [ 7514.302679] ata4.00: configured for UDMA/133
Feb 21 21:58:17 debian-nas kernel: [ 7514.313408] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300)
Feb 21 21:58:17 debian-nas kernel: [ 7514.314893] ata1.00: configured for UDMA/133
Feb 21 21:58:17 debian-nas kernel: [ 7514.315053] ata3.00: configured for UDMA/133
Feb 21 21:58:17 debian-nas kernel: [ 7514.317100] PM: Using 3 thread(s) for compression
Feb 21 21:58:17 debian-nas kernel: [ 7514.317105] PM: Compressing and saving image data (757450 pages)...
Feb 21 21:58:17 debian-nas kernel: [ 7514.317173] PM: Image saving progress:   0%
Feb 21 21:58:17 debian-nas kernel: [ 7514.879418] PM: Image saving progress:  10%
Feb 21 21:58:17 debian-nas kernel: [ 7515.468475] PM: Image saving progress:  20%
Feb 21 21:58:17 debian-nas kernel: [ 7516.065874] PM: Image saving progress:  30%
Feb 21 21:58:17 debian-nas kernel: [ 7516.653725] PM: Image saving progress:  40%
Feb 21 21:58:17 debian-nas kernel: [ 7516.991739] r8169 0000:03:00.0 enp3s0: Link is Up - 1Gbps/Full - flow control rx/tx
Feb 21 21:58:17 debian-nas kernel: [ 7517.267825] PM: Image saving progress:  50%
Feb 21 21:58:17 debian-nas kernel: [ 7517.958963] PM: Image saving progress:  60%
Feb 21 21:58:17 debian-nas kernel: [ 7518.508825] PM: Image saving progress:  70%
Feb 21 21:58:17 debian-nas kernel: [ 7518.762063] PM: hibernation: Wrote 3029800 kbytes in 4.44 seconds (682.38 MB/s)
Feb 21 21:58:17 debian-nas kernel: [ 7518.917059] PM: hibernation: Basic memory bitmaps freed
Feb 21 21:58:17 debian-nas kernel: [ 7518.917063] OOM killer enabled.
Feb 21 21:58:17 debian-nas kernel: [ 7518.917064] Restarting tasks ... done.
Feb 21 21:58:17 debian-nas kernel: [ 7518.923697] video LNXVIDEO:00: Restoring backlight state
Feb 21 21:58:17 debian-nas kernel: [ 7518.923730] PM: hibernation: hibernation exit
Feb 21 21:58:17 debian-nas systemd-sleep[26025]: Failed to suspend system. System resumed again: No space left on device
Feb 21 21:58:17 debian-nas systemd[1]: Starting watchdog daemon...
Feb 21 21:58:17 debian-nas watchdog[26107]: starting daemon (5.15):
Feb 21 21:58:17 debian-nas watchdog[26107]: int=1s realtime=yes sync=no load=0,0,0 soft=no
Feb 21 21:58:17 debian-nas watchdog[26107]: memory not checked
Feb 21 21:58:17 debian-nas watchdog[26107]: ping: no machine to check
Feb 21 21:58:17 debian-nas watchdog[26107]: file: no file to check
Feb 21 21:58:17 debian-nas watchdog[26107]: pidfile: no server process to check
Feb 21 21:58:17 debian-nas watchdog[26107]: interface: no interface to check
Feb 21 21:58:17 debian-nas watchdog[26107]: temperature: no sensors to check
Feb 21 21:58:17 debian-nas watchdog[26107]: no test binary files
Feb 21 21:58:17 debian-nas watchdog[26107]: no repair binary files
Feb 21 21:58:17 debian-nas watchdog[26107]: error retry time-out = 60 seconds
Feb 21 21:58:17 debian-nas watchdog[26107]: repair attempts = 1
Feb 21 21:58:17 debian-nas watchdog[26107]: alive=/dev/watchdog heartbeat=[none] to=root no_act=no force=no
Feb 21 21:58:17 debian-nas watchdog[26107]: watchdog now set to 60 seconds
Feb 21 21:58:17 debian-nas watchdog[26107]: hardware watchdog identity: wdat_wdt
Feb 21 21:58:17 debian-nas systemd[1]: Started watchdog daemon.
Feb 21 21:58:17 debian-nas systemd-sleep[26025]: /dev/sdb:
Feb 21 21:58:17 debian-nas systemd-sleep[26025]:  setting Advanced Power Management level to 0xfe (254)
Feb 21 21:58:17 debian-nas systemd-sleep[26025]:  APM_level#011= 254
Feb 21 21:58:17 debian-nas systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=1/FAILURE
Feb 21 21:58:17 debian-nas systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'.
Feb 21 21:58:17 debian-nas systemd[1]: Failed to start Hibernate.
Feb 21 21:58:17 debian-nas systemd[1]: Dependency failed for Hibernate.
Feb 21 21:58:17 debian-nas systemd[1]: hibernate.target: Job hibernate.target/start failed with result 'dependency'.
Feb 21 21:58:17 debian-nas systemd[1]: Stopped target Sleep.
Feb 21 21:58:17 debian-nas systemd[1]: Started openmediavault-autoshutdown plugin service.
Feb 21 22:00:01 debian-nas CRON[26422]: (root) CMD (/usr/sbin/omv-mkrrdgraph >/dev/null 2>&1)

Alles anzeigen

wtuppa · 22. Februar 2021

wieso hast du als Ausschaltbefehl "Ruhezustand". Das klingt nicht nach echtem Ausschalten. Da legt er ein Image vom RAM auf die Disk und das hat bei dir Probleme:

Zitat von tauchvogel

Feb 21 21:58:17 debian-nas kernel: [ 7513.776889] PM: hibernation: Creating image:
Feb 21 21:58:17 debian-nas kernel: [ 7513.920782] PM: hibernation: Need to copy 755973 pages
Feb 21 21:58:17 debian-nas kernel: [ 7513.920786] PM: hibernation: Normal pages needed: 755973 + 1024, available pages: 1250107
Feb 21 21:58:17 debian-nas kernel: [ 7514.748465] PM: hibernation: Image created (755973 pages copied)

und dann geht ihm auch noch der Speicher aus...

Zitat von tauchvogel

Feb 21 21:58:17 debian-nas kernel: [ 7518.508825] PM: Image saving progress: 70%
Feb 21 21:58:17 debian-nas kernel: [ 7518.762063] PM: hibernation: Wrote 3029800 kbytes in 4.44 seconds (682.38 MB/s)
Feb 21 21:58:17 debian-nas kernel: [ 7518.917059] PM: hibernation: Basic memory bitmaps freed
Feb 21 21:58:17 debian-nas kernel: [ 7518.917063] OOM killer enabled.
Feb 21 21:58:17 debian-nas kernel: [ 7518.917064] Restarting tasks ... done. Feb 21 21:58:17 debian-nas kernel: [ 7518.923697] video LNXVIDEO:00: Restoring backlight state
Feb 21 21:58:17 debian-nas kernel: [ 7518.923730] PM: hibernation: hibernation exit
Feb 21 21:58:17 debian-nas systemd-sleep[26025]: Failed to suspend system. System resumed again: No space left on device
Feb 21 21:58:17 debian-nas systemd[1]: Starting watchdog daemon...

Alles anzeigen

und damit fährt er nicht runter (Kompremmierung ist nur bis 70% gekommen). Wieso schaltest du nicht ganz aus? Ist dir dann die Hochlaufzeit zu lange?

also wenn du bei "Ruhezustand/Hibernate" bleiben willst, entweder Platz auf der Systemdisk schaffen oder die Kompression ausschalten, falls du keine swap partition hast (oder diese zu klein ist) [ist bei dir der Fall, da er in eine Datei speichert].

tauchvogel · 22. Februar 2021

Zitat von wtuppa

wieso hast du als Ausschaltbefehl "Ruhezustand". Das klingt nicht nach echtem Ausschalten. Da legt er ein Image vom RAM auf die Disk und das hat bei dir Probleme:
und dann geht ihm auch noch der Speicher aus...
und damit fährt er nicht runter (Kompremmierung ist nur bis 70% gekommen). Wieso schaltest du nicht ganz aus? Ist dir dann die Hochlaufzeit zu lange?
also wenn du bei "Ruhezustand/Hibernate" bleiben willst, entweder Platz auf der Systemdisk schaffen oder die Kompression ausschalten, falls du keine swap partition hast (oder diese zu klein ist) [ist bei dir der Fall, da er in eine Datei speichert].

Ich möchte gerne WOL nutzen. Das heisst, wenn erst einmal jemand im internen Netzwerk auf den Server zugreifen möchte, wird dieser per WOL Befehl geweckt. Das wird in Tutorials auch empfohlen.

Wenn der Server doch ganz herunterfährt, wie wecke ich ihn auf?

Also wenn ich Ruhezustand oder Unterbrechen nutzen möchte, dann muss die Kompression ausgeschaltet werden?

Eine Kompression hatte ich nicht eingerichtet. Bei der zuerst durchgeführten Debian Installation habe ich ein home Verzeichnis eingerichtet.

wtuppa · 22. Februar 2021

Wenn du ganz herunterfährst (also Off), bleibt die Netzwerkkarte unter Spannung, damit sie WOL Pakete erkennen kann (und nur die, keine Verbeitung und sonst nichts). Im Linux sollte dass automatisch eingestellt sein (eventuell mit ethtool checken).Unter Umstaenden musst du im BIOS aber auch noch was aktivieren (Einschalten über ...).

Ich habe das bei mir so am Laufen.

kurze Frage: wer sendet bei dir die WOL Pakete?

tauchvogel · 22. Februar 2021

Wenn ich am Rechner sitze, dann per WOL Befehl und der MAC Adresse des Server über das Terminal.

Aber auch per WOL App.

wtuppa · 22. Februar 2021

sollte beides funktionieren. Ich mache es nur über LAN, aber am Handy hat damals auch die APP funktioniert.

tauchvogel · 22. Februar 2021

Ich habe folgendes mal probiert. Fail2ban, minidlna, antivir deaktiviert.

Dann habe ich komischerweise immer wieder mal Portainer mit dem Plex Mediaserver im Hinterkopf gehabt, dass da etwas ist, das das System wach hält.

Ich habe Portainer mit Plex komplett deinstalliert.

Und prompt ging nach der eingestellten Wartezeit in den Ruhestand.

Kann es sein, dass Plex das System wach gehalten hat? Oder ein Plugin?

wtuppa · 22. Februar 2021

minidlna hatte ich auch mal, da hat es funktioniert.

wie Portainer sich verhalten, kann ich leider nicht beurteilen.

Autoshutdown funktioniert nicht

Jetzt mitmachen!

Teilen

Tags