Beiträge von Blabla
-
-
how sould I update? I read a post where you suggest to not use the command omv-dist-upgrade.
So How I'm supposed to updatE? -
So you think that I can install the kernel without waiting for an already compiled version?
-
Actually I have some problems with suspension and hibernation, because I have haswell. I was thinking about install the latest 4.7 for the better support
-
What's the difference between the custom kernel and installing the classic one?
-
Just a question : why it's so complicated to install a kernel? On Ubuntu I never had a problem simply installing it
-
I'll try to disable those things tonight! Thanks!
-
Which one you recommend?
-
this is my crontab
Code# m h dom mon dow user command 17 * * * * root cd / && run-parts --report /etc/cron.hourly 25 6 * * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.daily ) 47 6 * * 7 root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.weekly ) 52 6 1 * * root test -x /usr/sbin/anacron || ( cd / && run-parts --report /etc/cron.monthly ) #
I made the scheduled jobs into the web interface:
daily->root ->/usr/sbin/rtcwake -m disk -s 72000
is this correct? -
Hi guys.
I put into standby my omv pc and after that it doesn't wake up anymore!
If I go to the Web interface it gave me the error 403 forbidden, and I can't event connect with putty!
So I shot some photos of what I saw right after I connected my monitor at the Nas
I have the latest stable version with kernel 4.5.7 because the default one doesn't support my chipset (h170).
Here's the photoshttp://i.imgur.com/zncNFqC.jpg
http://imgur.com/a/OR9kB
http://i.imgur.com/BnItNoX.jpg
http://i.imgur.com/qSPqwOa.jpgI rebooted and now it works fine, but still what was the problem?
-
Hi guys.
I put into standby my omv pc and after that it doesn't wake up anymore!
If I go to the Web interface it gave me the error 403 forbidden, and I can't event connect with putty!
So I shot some photos of what I saw right after I connected my monitor at the Nas
I have the latest stable version with kernel 4.5.7 because the default one doesn't support my chipset (h170).
Here's the photoshttp://i.imgur.com/zncNFqC.jpg
http://imgur.com/a/OR9kB
http://i.imgur.com/BnItNoX.jpg
http://i.imgur.com/qSPqwOa.jpg -
Yes.
Some motherboard support hibernation (S4), & sleep (S3), while others are not.
Try it out on your system, and see which method is best for you.Here's an example of my sleep/wake up schedule in /ect/crontab:
Thanks! so whats should I write to wake up at 6PM during week, and 8AM during weekend?
for what I read your lane include the shutdown too right? -
Is enabled on both motherboard and OMV
you mean "Scheduled jobs"? -
1) scheduled is still better for me, but yeah, wol is still good
2) yes -
-
Hi at all guys!
I was thinking about setting a timer for the shutdown and wakeup of my OMV. Is this possible?
Also, I don't get why, but even if both my motherboard and OMV have WoL enabled, I can't wake it up
Can someone help me with both the things? -
how can I know if the command is working? I deleted both .1 logs, but a sill have a 8,2GB syslog
-
4.5.7, because I have the latest chipset, and the 3.16 is not compatible with them
-
I would delete the .1 files to start. Those are archives. I would also look in syslog to see what is logging so much. Maybe by posting tail -n 200 /var/log/syslog, I could tell.
I did a Tail on syslog.1 and kern.log.1,
this was the error that i found in both of them:CodeJul 16 11:09:07 NAS kernel: [ 320.973111] ACPI Exception: AE_NOT_FOUND, while evaluating GPE method [_L6F] (20160108/evgpe-592) Jul 16 11:09:07 NAS kernel: [ 320.974151] ACPI Error: [PGRT] Namespace lookup failure, AE_NOT_FOUND (20160108/psargs-359)
with your command this are the error that i had:
Code
Alles anzeigenJul 18 00:59:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 00:59:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:00:01 NAS /USR/SBIN/CRON[14207]: (root) CMD (/usr/sbin/omv-mkgraph >/dev/null 2>&1) Jul 18 01:00:01 NAS rrdcached[2632]: Received FLUSHALL Jul 18 01:00:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:00:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:01:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:01:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:02:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:02:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:03:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:03:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:04:10 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:04:12 NAS rrdcached[2632]: flushing old values Jul 18 01:04:12 NAS rrdcached[2632]: rotating journals Jul 18 01:04:12 NAS rrdcached[2632]: started new journal /var/lib/rrdcached/journal/rrd.journal.1468796652.581411 Jul 18 01:04:12 NAS rrdcached[2632]: removing old journal /var/lib/rrdcached/journal/rrd.journal.1468789452.581409 Jul 18 01:04:40 NAS monit[2940]: 'rootfs' space usage 100.0% matches resource limit [space usage>80.0%] Jul 18 01:17:01 NAS /USR/SBIN/CRON[14562]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) Jul 18 01:17:01 NAS postfix/postsuper[14565]: fatal: scan_dir_push: open directory hold: No such file or directory Jul 18 02:09:01 NAS /USR/SBIN/CRON[15490]: (root) CMD ( [ -x /usr/lib/php5/maxlifetime ] && [ -x /usr/lib/php5/sessionclean ] && [ -d /var/lib/php5 ] && /usr/lib/php5/sessionclean /var/lib/php5 $(/usr/lib/php5/maxlifetime)
-