+- MinimServer Forum (https://forum.minimserver.com)
+-- Forum: MinimServer (/forumdisplay.php?fid=1)
+--- Forum: Support (/forumdisplay.php?fid=4)
+--- Thread: Clear Minimserver Log Manually (/showthread.php?tid=1244)
Pages: 1 2
Clear Minimserver Log Manually - Foxman50 - 04-01-2014 10:16
Is there a way to clear Minimserver log manually on my NAS rather than using Minimwatch. Something has happened after applying the update to Minimwatch last night. Ive deleted and reinstalled minimwatch but it just keeps locking up.
When i look on my NAS i can see a heap of info in the log but it doesnt give the option to clear it. Can it be done from command line, if so where and which file. Do i delete the file or open it and clear its contents.
Graeme
RE: Clear Minimserver Log Manually - simoncn - 04-01-2014 11:59
(04-01-2014 10:16)Foxman50 Wrote: Is there a way to clear Minimserver log manually on my NAS rather than using Minimwatch. Something has happened after applying the update to Minimwatch last night. Ive deleted and reinstalled minimwatch but it just keeps locking up.
When i look on my NAS i can see a heap of info in the log but it doesnt give the option to clear it. Can it be done from command line, if so where and which file. Do i delete the file or open it and clear its contents.
Graeme
You can delete the minimserver.log file manually at any time, and MinimServer will recreate it the next time it writes something to the log.
RE: Clear Minimserver Log Manually - Foxman50 - 04-01-2014 12:09
(04-01-2014 11:59)simoncn Wrote:(04-01-2014 10:16)Foxman50 Wrote: Is there a way to clear Minimserver log manually on my NAS rather than using Minimwatch. Something has happened after applying the update to Minimwatch last night. Ive deleted and reinstalled minimwatch but it just keeps locking up.
When i look on my NAS i can see a heap of info in the log but it doesnt give the option to clear it. Can it be done from command line, if so where and which file. Do i delete the file or open it and clear its contents.
Graeme
You can delete the minimserver.log file manually at any time, and MinimServer will recreate it the next time it writes something to the log.
Can you tell me which directory on the nas it is stored, Synology NAS, and which file i should delete
RE: Clear Minimserver Log Manually - simoncn - 04-01-2014 12:13
(04-01-2014 12:09)Foxman50 Wrote: Can you tell me which directory on the nas it is stored, Synology NAS, and which file i should delete
/volume1/homes/minimserver/appData/minimserver.log
RE: Clear Minimserver Log Manually - Foxman50 - 04-01-2014 14:41
(04-01-2014 12:13)simoncn Wrote:(04-01-2014 12:09)Foxman50 Wrote: Can you tell me which directory on the nas it is stored, Synology NAS, and which file i should delete
/volume1/homes/minimserver/appData/minimserver.log
It seems that an update to Avast Antivirus software is causing all sorts of issues with Minimwatch. Disabling Avast makes everything work again. Not sure what its doing. I copied the log from Minimserver if its any use but very long
RE: Clear Minimserver Log Manually - simoncn - 04-01-2014 16:05
(04-01-2014 14:41)Foxman50 Wrote: It seems that an update to Avast Antivirus software is causing all sorts of issues with Minimwatch. Disabling Avast makes everything work again. Not sure what its doing. I copied the log from Minimserver if its any use but very long
Thanks for this information. It might help other users who have reported similar issues with MinimWatch locking up.
If the problem is with MinimWatch, I would need to see the MinimWatch log (on your PC or Mac), not the MinimServer log (on your NAS).
RE: Clear Minimserver Log Manually - Foxman50 - 04-01-2014 17:40
(04-01-2014 16:05)simoncn Wrote:(04-01-2014 14:41)Foxman50 Wrote: It seems that an update to Avast Antivirus software is causing all sorts of issues with Minimwatch. Disabling Avast makes everything work again. Not sure what its doing. I copied the log from Minimserver if its any use but very long
Thanks for this information. It might help other users who have reported similar issues with MinimWatch locking up.
If the problem is with MinimWatch, I would need to see the MinimWatch log (on your PC or Mac), not the MinimServer log (on your NAS).
Ok here's what happens when Avast is running.
Start Minimwatch, it turns green and i can look at minimwatch properties and log etc. I can close Minimwatch at this point without issue.
Start Minimwatch and if i try to open Minimserver properties, the properties window does not appear and im unable to do anything else in Minimwatch. I cant close it, and it doesnt even appear in task manager but stays in system tray. Im having to reboot the pc to get it to go.
Nothing is written into the log, in fact i cant find Minimwatch.log on my pc, which is Win 8.1 netbook, but nothing appears in Minimwatch log within Minimwatch. When i look after the reboot it only contains info following the reboot not previous to it.
After the pc reboot, if i restart Minimwatch it just sits there greyed out in the task bar. I then exit it and try to reopen Minimwatch and nothing happens, no icon at all.
Not sure how i got out of this before, but will try deleting Minmserver.log on the NAS ans restarting Minimserver. Will see
Ah OK its those little java applets i have to kill. Anyway not sure what i can supply to you. I just have to make sure Avast is disabled before i start Minimwatch
RE: Clear Minimserver Log Manually - simoncn - 04-01-2014 18:01
(04-01-2014 17:40)Foxman50 Wrote: Ok here's what happens when Avast is running.
Start Minimwatch, it turns green and i can look at minimwatch properties and log etc. I can close Minimwatch at this point without issue.
Start Minimwatch and if i try to open Minimserver properties, the properties window does not appear and im unable to do anything else in Minimwatch. I cant close it, and it doesnt even appear in task manager but stays in system tray. Im having to reboot the pc to get it to go.
Nothing is written into the log, in fact i cant find Minimwatch.log on my pc, which is Win 8.1 netbook, but nothing appears in Minimwatch log within Minimwatch. When i look after the reboot it only contains info following the reboot not previous to it.
After the pc reboot, if i restart Minimwatch it just sits there greyed out in the task bar. I then exit it and try to reopen Minimwatch and nothing happens, no icon at all.
Not sure how i got out of this before, but will try deleting Minmserver.log on the NAS ans restarting Minimserver. Will see
Ah OK its those little java applets i have to kill. Anyway not sure what i can supply to you. I just have to make sure Avast is disabled before i start Minimwatch
The problem is occurring when MinimWatch attempts to send a request to MinimServer. It sounds like Avast thinks this is unsafe and is blocking all such communications from then on. Is Avast running on the PC or on the NAS?
RE: Clear Minimserver Log Manually - Foxman50 - 04-01-2014 18:06
(04-01-2014 18:01)simoncn Wrote:(04-01-2014 17:40)Foxman50 Wrote: Ok here's what happens when Avast is running.
Start Minimwatch, it turns green and i can look at minimwatch properties and log etc. I can close Minimwatch at this point without issue.
Start Minimwatch and if i try to open Minimserver properties, the properties window does not appear and im unable to do anything else in Minimwatch. I cant close it, and it doesnt even appear in task manager but stays in system tray. Im having to reboot the pc to get it to go.
Nothing is written into the log, in fact i cant find Minimwatch.log on my pc, which is Win 8.1 netbook, but nothing appears in Minimwatch log within Minimwatch. When i look after the reboot it only contains info following the reboot not previous to it.
After the pc reboot, if i restart Minimwatch it just sits there greyed out in the task bar. I then exit it and try to reopen Minimwatch and nothing happens, no icon at all.
Not sure how i got out of this before, but will try deleting Minmserver.log on the NAS ans restarting Minimserver. Will see
Ah OK its those little java applets i have to kill. Anyway not sure what i can supply to you. I just have to make sure Avast is disabled before i start Minimwatch
The problem is occurring when MinimWatch attempts to send a request to MinimServer. It sounds like Avast thinks this is unsafe and is blocking all such communications from then on. Is Avast running on the PC or on the NAS?
Its on the pc so its no hassle to stop Avast while i use Minimwatch. Its just odd how it locks Minimwatch up. Normally in task manager the Minimwatch icon appears when the app is running. When Minimwatch locks up this icon is replaced by the normal java icon. I just noticed as i kept trying to open Minimwatch another java icon appeared. If that makes sense
RE: Clear Minimserver Log Manually - Foxman50 - 04-01-2014 18:15
This is the last section from the minimserver log. No idea if it shows anything.
16:34:54.502 Thread-73: Monitor response: SaveProperty
16:34:54.502 Thread-73: ErrorMsg=
16:34:54.506 Thread-74: ohNet: WriteChanges for subscription 419fb6d3-e259-48ee-8354-691c2801548e-7 seq - 2
16:34:54.508 Thread-73: ohNet: Completed action: SaveProperty
16:34:54.521 Thread-72: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Log-1/control
16:34:54.521 Thread-72: ohNet: Action called: GetLogData
16:34:54.523 Thread-72: ohNet: Completed action: GetLogData
16:35:05.927 Thread-71: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Log-1/control
16:35:05.928 Thread-71: ohNet: Action called: SetLogStart
16:35:05.931 Thread-71: Monitor action: SetLogStart
16:35:05.931 Thread-71: version=1, adapter=192.168.1.100, uriPrefix=http://192.168.1.100:9791/419fb6d3-e259-48ee-8354-691c2801548e/Upnp/resource/, clientEndpoint=192.168.1.84:49645
16:35:05.931 Thread-71: StartPosition=250715
16:35:05.933 Thread-76: ohNet: WriteChanges for subscription 419fb6d3-e259-48ee-8354-691c2801548e-7 seq - 3
16:35:05.938 Thread-77: ohNet: WriteChanges for subscription 419fb6d3-e259-48ee-8354-691c2801548e-7 seq - 4
16:35:05.939 Thread-77: ohNet: Found no changes to publish
16:35:05.942 Thread-71: Monitor action complete: SetLogStart
16:35:05.943 Thread-71: ohNet: Completed action: SetLogStart
16:35:05.945 Thread-70: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Log-1/control
16:35:05.945 Thread-70: ohNet: Action called: GetLogData
16:35:05.947 Thread-70: ohNet: Completed action: GetLogData
16:35:05.954 Thread-73: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Log-1/control
16:35:05.955 Thread-73: ohNet: Action called: GetLogStart
16:35:05.956 Thread-73: Log action: GetLogStart
16:35:05.956 Thread-73: version=1, adapter=192.168.1.100, uriPrefix=http://192.168.1.100:9791/419fb6d3-e259-48ee-8354-691c2801548e/Upnp/resource/, clientEndpoint=192.168.1.84:49647
16:35:05.957 Thread-73: Log response: GetLogStart
16:35:05.957 Thread-73: StartPosition=250715
16:35:05.957 Thread-73: ohNet: Completed action: GetLogStart
16:35:05.983 Thread-75: ohNet: WriteChanges for subscription 419fb6d3-e259-48ee-8354-691c2801548e-7 seq - 4
16:35:05.994 Thread-72: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Log-1/control
16:35:05.994 Thread-72: ohNet: Action called: GetLogData
16:35:05.995 Thread-72: ohNet: Completed action: GetLogData
16:35:08.424 Thread-71: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Log-1/control
16:35:08.424 Thread-71: ohNet: Action called: SetLogStart
16:35:08.426 Thread-71: Monitor action: SetLogStart
16:35:08.426 Thread-71: version=1, adapter=192.168.1.100, uriPrefix=http://192.168.1.100:9791/419fb6d3-e259-48ee-8354-691c2801548e/Upnp/resource/, clientEndpoint=192.168.1.84:49649
16:35:08.426 Thread-71: StartPosition=251382
16:35:08.427 Thread-71: Monitor action complete: SetLogStart
16:35:08.428 Thread-71: ohNet: Completed action: SetLogStart
16:35:08.429 Thread-74: ohNet: WriteChanges for subscription 419fb6d3-e259-48ee-8354-691c2801548e-7 seq - 5
16:35:08.440 Thread-76: ohNet: WriteChanges for subscription 419fb6d3-e259-48ee-8354-691c2801548e-7 seq - 6
16:35:08.440 Thread-76: ohNet: Found no changes to publish
16:35:08.445 Thread-70: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Log-1/control
16:35:08.446 Thread-70: ohNet: Action called: GetLogData
16:35:08.447 Thread-70: ohNet: Completed action: GetLogData
16:35:08.455 Thread-73: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Log-1/control
16:35:08.455 Thread-73: ohNet: Action called: GetLogStart
16:35:08.457 Thread-73: Log action: GetLogStart
16:35:08.457 Thread-73: version=1, adapter=192.168.1.100, uriPrefix=http://192.168.1.100:9791/419fb6d3-e259-48ee-8354-691c2801548e/Upnp/resource/, clientEndpoint=192.168.1.84:49651
16:35:08.457 Thread-73: Log response: GetLogStart
16:35:08.457 Thread-73: StartPosition=251382
16:35:08.458 Thread-73: ohNet: Completed action: GetLogStart
16:35:08.483 Thread-77: ohNet: WriteChanges for subscription 419fb6d3-e259-48ee-8354-691c2801548e-7 seq - 6
16:35:08.518 Thread-72: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Log-1/control
16:35:08.518 Thread-72: ohNet: Action called: GetLogData
16:35:08.519 Thread-72: ohNet: Completed action: GetLogData
16:35:11.437 Thread-71: ohNet: Method: POST, uri: /419fb6d3-e259-48ee-8354-691c2801548e/jminim.org-Monitor-1/control
16:35:11.438 Thread-71: ohNet: Action called: SaveProperty
16:35:11.440 Thread-71: Monitor action: SaveProperty
16:35:11.440 Thread-71: version=1, adapter=192.168.1.100, uriPrefix=http://192.168.1.100:9791/419fb6d3-e259-48ee-8354-691c2801548e/Upnp/resource/, clientEndpoint=192.168.1.84:49653
16:35:11.440 Thread-71: ComponentName= PropertyName=logLevel PropertyValue=info
16:35:11.441 Thread-71: saveProperty: compName=null propName=logLevel propValue=info
16:35:11.443 Thread-75: ohNet: WriteChanges for subscription 419fb6d3-e259-48ee-8354-691c2801548e-7 seq - 7