MinimServer 0.71 is now available

[simoncn]

(20-04-2013 07:25)advr Wrote:  hi, after one night, this is the log

These logs contain a lot of messages from sabnzbd. I don't see any messages from MinimServer.

[advr]

(20-04-2013 08:02)simoncn Wrote:  

(20-04-2013 07:25)advr Wrote:  hi, after one night, this is the log

These logs contain a lot of messages from sabnzbd. I don't see any messages from MinimServer.

thanks!

with what can you read the file? I couldn't do it with a any program....

sabnzbd is running for months now and still the same version and configuration but I can shut it down for a while and see what happens.

Ad.

[advr]

(20-04-2013 08:02)simoncn Wrote:  

(20-04-2013 07:25)advr Wrote:  hi, after one night, this is the log

These logs contain a lot of messages from sabnzbd. I don't see any messages from MinimServer.

I managed it to read..

Yes much SABNZBD but as always it reads the USB stick and not a disk.
That's a familiar trick to get the Synilogy into hybernate. Using it for years now.

So something else is doing it but what?

[winxi]

(20-04-2013 11:52)advr Wrote:  

(20-04-2013 08:02)simoncn Wrote:  

(20-04-2013 07:25)advr Wrote:  hi, after one night, this is the log

These logs contain a lot of messages from sabnzbd. I don't see any messages from MinimServer.

I managed it to read..

Yes much SABNZBD but as always it reads the USB stick and not a disk.
That's a familiar trick to get the Synilogy into hybernate. Using it for years now.

So something else is doing it but what?

From the kernel log, it seems that SABnzbd prevents the NAS from hibernating. In the Synology FAQ, SABnzbd is explicitely stated as a 3rd party package which may cause hibernation problems.
The only way to prove this will be to deactivate or uninstall this package and to see whether the problem persists.

[advr]

(20-04-2013 12:07)winxi Wrote:  From the kernel log, it seems that SABnzbd prevents the NAS from hibernating. In the Synology FAQ, SABnzbd is explicitely stated as a 3rd party package which may cause hibernation problems.
The only way to prove this will be to deactivate or uninstall this package and to see whether the problem persists.

It's a known problem with the trick to let SABNZBD search at a USB stick no problem!

Also running SABNZBD for years at several DS types and never problem but I will stop it for a while.

[advr]

Apr 21 00:30:29 kernel: [111989.352785] [/etc/passwd] opened by pid 27361 [u-ash), comm:(ash)]
Apr 21 00:30:34 kernel: [111994.363947] [/var/run/utmp] opened by pid 27294 [u:(telnetd), comm:(telnetd)]
Apr 21 00:32:39 kernel: [112118.988999] [/var/log/log.smbd] opened by pid 20811 [u/usr/syno/sbin/smbd), comm:(smbd)]
Apr 21 00:35:39 kernel: [112299.038196] [/var/log/log.smbd] opened by pid 20811 [u/usr/syno/sbin/smbd), comm:(smbd)]
Apr 21 00:38:39 kernel: [112479.087367] [/var/log/log.smbd] opened by pid 20811 [u/usr/syno/sbin/smbd), comm:(smbd)]
Apr 21 00:41:39 kernel: [112659.197512] [/var/log/log.smbd] opened by pid 20811 [u/usr/syno/sbin/smbd), comm:(smbd)]
Apr 21 00:44:39 kernel: [112839.248696] [/var/log/log.smbd] opened by pid 20811 [u/usr/syno/sbin/smbd), comm:(smbd)]
Apr 21 00:47:39 kernel: [113019.358850] [/var/log/log.smbd] opened by pid 20811 [u/usr/syno/sbin/smbd), comm:(smbd)]
Apr 21 02:03:21 kernel: [117559.046807] [/var/packages/MediaServer/target/etc/connmgrSCPD.xml] opened by pid 10013 [u/var/packages/MediaServer/targe), comm:(dms)]
Apr 21 03:45:19 kernel: [123674.190937] [/var/packages/MediaServer/target/etc/connmgrSCPD.xml] opened by pid 10013 [u/var/packages/MediaServer/targe), comm:(dms)]
Apr 21 10:07:04 kernel: [146570.556931] [/etc/passwd] opened by pid 14361 [u/usr/sbin/inetd), comm:(inetd)]

[advr]

Hibernation is SOLVED... after I went backto 0.63-5 my 412+ is hibernating again... so there must be something in 0.71 that is my 412+ prevents to hibernate and it's not logged by the synology...

I can't find it.

Maybe someone has the solution! :-)

[simoncn]

(22-04-2013 21:09)advr Wrote:  Hibernation is SOLVED... after I went backto 0.63-5 my 412+ is hibernating again... so there must be something in 0.71 that is my 412+ prevents to hibernate and it's not logged by the synology...

I can't find it.

Maybe someone has the solution! :-)

The only possibility I can think of is that MinimServer might be writing some output to the file /homes/minimserver/appData/minimserver.log or the file /homes/minimserver/appData/minimserver-out.log. If you get a chance to try 0.71 again, can you look at these files to see if any output is being written when MinimServer is idle?

[advr]

(23-04-2013 09:03)simoncn Wrote:  The only possibility I can think of is that MinimServer might be writing some output to the file /homes/minimserver/appData/minimserver.log or the file /homes/minimserver/appData/minimserver-out.log. If you get a chance to try 0.71 again, can you look at these files to see if any output is being written when MinimServer is idle?

Of course I will try 0.71 again and look at the files.

I will try it tonight!

Ad.

[advr]

This I am seeing in the minimserver.log file:
18:10:19.927 Thread-10: ohNet: SSDP Multicast HttpError
18:10:19.928 Thread-11: ohNet: SSDP Multicast HttpError
18:10:39.928 Thread-10: ohNet: SSDP Multicast HttpError
18:10:39.928 Thread-11: ohNet: SSDP Multicast HttpError
18:10:49.929 Thread-11: ohNet: SSDP Multicast HttpError
18:10:49.929 Thread-10: ohNet: SSDP Multicast HttpError
18:10:59.187 Thread-16: ohNet: Device 4e06ad42-4931-4c01-923b-ddfb8d53acd9 starting to send alive notifications.
18:11:09.929 Thread-10: ohNet: SSDP Multicast HttpError
18:11:09.929 Thread-11: ohNet: SSDP Multicast HttpError
18:11:19.929 Thread-11: ohNet: SSDP Multicast HttpError
18:11:19.930 Thread-10: ohNet: SSDP Multicast HttpError