<< return to Vizycam.com

Vizy Server hang

I was working on a new app this afternoon and copied some files between my Mac and the Vizy shared drive. The Vizy web app hung up right away and wouldn’t restart even after a reboot.

“sudo journalctl -f --unit Vizy-server” returned:

Mar 31 16:44:43 vizy systemd[1]: Started Vizy server.
Mar 31 16:44:46 vizy python3[1903]:
Mar 31 16:44:46 vizy python3[1903]: Unhandled exception:
Mar 31 16:44:46 vizy python3[1903]: Traceback (most recent call last):
Mar 31 16:44:46 vizy python3[1903]: File “/home/pi/vizy/scripts/vizy_server”, line 4, in
Mar 31 16:44:46 vizy python3[1903]: vv = VizyVisor()
Mar 31 16:44:46 vizy python3[1903]: File “/usr/local/lib/python3.7/dist-packages/vizy-0.1.98-py3.7.egg/vizy/vizyvisor.py”, line 87, in init
Mar 31 16:44:46 vizy python3[1903]: self.apps_dialog = AppsDialog(self, PMASK_CONSOLE, PMASK_APPS)
Mar 31 16:44:46 vizy python3[1903]: File “/usr/local/lib/python3.7/dist-packages/vizy-0.1.98-py3.7.egg/vizy/appsdialog.py”, line 91, in init
Mar 31 16:44:46 vizy python3[1903]: self.update_progs()
Mar 31 16:44:46 vizy python3[1903]: File “/usr/local/lib/python3.7/dist-packages/vizy-0.1.98-py3.7.egg/vizy/appsdialog.py”, line 317, in update_progs
Mar 31 16:44:46 vizy python3[1903]: self.progs[k] = [self._app_info(appdir, f) for f in os.listdir(appdir)]
Mar 31 16:44:46 vizy python3[1903]: File “/usr/local/lib/python3.7/dist-packages/vizy-0.1.98-py3.7.egg/vizy/appsdialog.py”, line 317, in
Mar 31 16:44:46 vizy python3[1903]: self.progs[k] = [self._app_info(appdir, f) for f in os.listdir(appdir)]
Mar 31 16:44:46 vizy python3[1903]: File “/usr/local/lib/python3.7/dist-packages/vizy-0.1.98-py3.7.egg/vizy/appsdialog.py”, line 240, in app_info
Mar 31 16:44:46 vizy python3[1903]: pyfiles = [f for f in os.listdir(path) if f.endswith(".py")]
Mar 31 16:44:46 vizy python3[1903]: NotADirectoryError: [Errno 20] Not a directory: '/home/pi/vizy/apps/.
.DS_Store’
Mar 31 16:44:46 vizy python3[1903]:
Mar 31 16:44:47 vizy systemd[1]: vizy-server.service: Main process exited, code=exited, status=1/FAILURE
Mar 31 16:44:47 vizy systemd[1]: vizy-server.service: Failed with result ‘exit-code’.
Mar 31 16:44:47 vizy systemd[1]: vizy-server.service: Service RestartSec=100ms expired, scheduling restart.
Mar 31 16:44:47 vizy systemd[1]: vizy-server.service: Scheduled restart job, restart counter is at 65.
Mar 31 16:44:47 vizy systemd[1]: Stopped Vizy server.

I was able to recover by deleting the hidden DS_store files that I unknowingly copied to the Vizy.

I’ll be careful in the future to make sure I don’t do that again, but maybe the Vizy software could handle this type of error case a bit better or you could add a warning for other Mac users somewhere in the docs?

Thanks,
Ed

Hmm. It wasn’t the copy that hung the server. I had the Vizy samba share of the pi folder mounted on my Mac. Just browsing to the apps folder hangs it until .DS_Store and ._.DS_Store are removed.

And here is a fix for it on the Mac side: https://support.apple.com/en-us/HT208209

It’ll prevent your Mac from writing those files. It’s per user and requires a log out / log in to take effect.

Hi Ed,
We need to make sure that these kinds of things don’t result in server crashes. This is good information – thanks :slight_smile:

Edward

1 Like