dlandon Posted January 3, 2021 Author Share Posted January 3, 2021 4 minutes ago, repomanz said: HI @dlandon Thank you. I tried that and still having issues with mariadb starting. I have 32gb installed and even with shm set at 24G (75%) I still get the error starting up db. Other suggestions? Delete your docker image, and the docker template and then go to apps and use the latest template and re-install the docker. Quote Link to comment
dlandon Posted January 3, 2021 Author Share Posted January 3, 2021 14 minutes ago, repomanz said: HI @dlandon Thank you. I tried that and still having issues with mariadb starting. I have 32gb installed and even with shm set at 24G (75%) I still get the error starting up db. Other suggestions? I did notice this however: Starting services... * Starting Apache httpd web server apache2 * * Starting MariaDB database server mysqld * Starting MariaDB database server mysqld Jan 3 15:54:29 2640f3f29b3b web_php[623]: FAT [Failed db connection to ] mariadb starting up twice? Were you using the master docker previously? Quote Link to comment
repomanz Posted January 3, 2021 Share Posted January 3, 2021 (edited) 5 minutes ago, dlandon said: Were you using the master docker previously? Was using the previous one defined in the template before this update. I didn't change anything there. Doing another re-install with the shm defined at the start to see if that does anything different. Update: no change after removing docker and image with fresh installation with shm set to 16g at the start of install. Edited January 3, 2021 by repomanz Quote Link to comment
dlandon Posted January 3, 2021 Author Share Posted January 3, 2021 40 minutes ago, hbrob said: I had a clean folder when this happened (I started completely from scratch when trying to troubleshoot). Manually adding the files to my hooks folder from the repo fixed this issue, but hooks still arent working. When trying to run this manually from the command line, I get "sudo: /var/lib/zmeventnotification/bin/zm_event_start.sh: command not found' At this point, I would like to just roll back to the previoys 18.04 version ( I still have my files from that install). Is there a way to do this so I can get it going again? Was working fine under my old install. I dont see any tags on your docker repo. Give me a bit. I think I found something. Quote Link to comment
repomanz Posted January 3, 2021 Share Posted January 3, 2021 21 minutes ago, dlandon said: Delete your docker image, and the docker template and then go to apps and use the latest template and re-install the docker. deleted docker, reinstalled with shm set to 16gb. No luck. is that the correct template URL? Quote Link to comment
Squid Posted January 3, 2021 Share Posted January 3, 2021 6 minutes ago, repomanz said: is that the correct template URL? Template URL's are always correct in the template. Assuming you install via Apps, the author actually cannot set it. Besides that, the entry is only used during updates and has no bearing whatsoever outside of that scenario and what happens when the container is updated. Quote Link to comment
Jokerigno Posted January 3, 2021 Share Posted January 3, 2021 Hi I followed @dlandon suggestion and redownloaded xml and recreated container leaving the rest as is. Now I have this error message when connecting to ui: Unable to connect to ZM db.SQLSTATE[HY000] [2002] No such file or directory How can I fix it? Quote Link to comment
dlandon Posted January 3, 2021 Author Share Posted January 3, 2021 A new docker is building that should fix the es issues. Quote Link to comment
texastoast_ Posted January 4, 2021 Share Posted January 4, 2021 Having the same issue as some others here. Removed the old image, ditched the old template and pulled all new versions down. MySql wont start. Currently have Shared mem set to 18GB. I see you're working on a new build, and I appreciate how quick you're working. Just throwing in more information. Quote Link to comment
dlandon Posted January 4, 2021 Author Share Posted January 4, 2021 3 minutes ago, texastoast_ said: Having the same issue as some others here. Removed the old image, ditched the old template and pulled all new versions down. MySql wont start. Currently have Shared mem set to 18GB. I see you're working on a new build, and I appreciate how quick you're working. Just throwing in more information. What files do you see in appdata/conf/? Quote Link to comment
texastoast_ Posted January 4, 2021 Share Posted January 4, 2021 3 minutes ago, dlandon said: What files do you see in appdata/conf/? I see a README and zm.default Quote Link to comment
repomanz Posted January 4, 2021 Share Posted January 4, 2021 13 minutes ago, texastoast_ said: I see a README and zm.default same here. I'm broke currently. Quote Link to comment
dlandon Posted January 4, 2021 Author Share Posted January 4, 2021 10 minutes ago, texastoast_ said: I see a README and zm.default Did you check your appdata paths if you used the new template? Click on more settings to see the paths. Quote Link to comment
repomanz Posted January 4, 2021 Share Posted January 4, 2021 2 minutes ago, dlandon said: Did you check your appdata paths if you used the new template? Click on more settings to see the paths. Quote Link to comment
texastoast_ Posted January 4, 2021 Share Posted January 4, 2021 4 minutes ago, dlandon said: Did you check your appdata paths if you used the new template? Click on more settings to see the paths. Paths are in-tact. Appdata Config Path: /mnt/user/dockerdata/Zoneminder Container Path: /config Data Path: /mnt/user/appdata/Zoneminder/data Container Path: /var/cache/zoneminder Quote Link to comment
repomanz Posted January 4, 2021 Share Posted January 4, 2021 (edited) @dlandon I renamed my zoneminder folder (appdata) and doing a completely new install. Not that I wanted to do that but wanted to test. I noticed something in the mysql folder relating to debian and I thought I saw a reference above that the new version uses ubuntu New version is building now (compiling opencv) but I took a look at the mysql directory and the debian flag file is debian-10.3.flag. Not sure if that matters or not but wanted to point it out. Edited January 4, 2021 by repomanz Quote Link to comment
dlandon Posted January 4, 2021 Author Share Posted January 4, 2021 Just now, repomanz said: @dlandon I renamed my zoneminder folder (appdata) and doing a completely new install. Not that I wanted to do that but wanted to test. I noticed something in the mysql folder relating to debian and I thought I saw a reference above that the new version uses ubuntu The previous version was also Ubuntu. Ubuntu is Debian based. I also did a new install without a problem. Quote Link to comment
repomanz Posted January 4, 2021 Share Posted January 4, 2021 (edited) 2 minutes ago, dlandon said: The previous version was also Ubuntu. Ubuntu is Debian based. I also did a new install without a problem. New version is building now (compiling opencv) but I took a look at the mysql directory and the debian flag file is debian-10.3.flag. Not sure if that matters or not but wanted to point it out. In my old directory it's 10.1 Edited January 4, 2021 by repomanz Quote Link to comment
texastoast_ Posted January 4, 2021 Share Posted January 4, 2021 @dlandon If I build into a new directory and stand up a second install, it runs no problem. Quote Link to comment
dlandon Posted January 4, 2021 Author Share Posted January 4, 2021 1 minute ago, repomanz said: New version is building now (compiling opencv) but I took a look at the mysql directory and the debian flag file is debian-10.3.flag. Not sure if that matters or not but wanted to point it out. 10.3 is the Maria db version. Quote Link to comment
repomanz Posted January 4, 2021 Share Posted January 4, 2021 1 minute ago, dlandon said: 10.3 is the Maria db version. In the old directory where I tried to update the flag file is 10.1. Maybe that's the issue? Quote Link to comment
dlandon Posted January 4, 2021 Author Share Posted January 4, 2021 1 minute ago, repomanz said: In the old directory where I tried to update the flag file is 10.1. Maybe that's the issue? Sorry, I was thinking of another docker of mine. Quote Link to comment
dlandon Posted January 4, 2021 Author Share Posted January 4, 2021 Those of you with database issues, it may be due to you restarting the docker and updating Zoneminder in the process. Zoneminder will get updated whenever the docker is restarted if there is a new version of Zoneminder. Part of the update to Zoeminder is an update to the database. If that failed because of the issues with shared memory, the database may have gotten corrupted. 1 Quote Link to comment
repomanz Posted January 4, 2021 Share Posted January 4, 2021 8 minutes ago, dlandon said: Sorry, I was thinking of another docker of mine. No problem. Is there a way we can debug this? My new install completed including a fresh zoneminder app data directory and it comes up with no problem (except all my configurations / cameras are gone). Quote Link to comment
dlandon Posted January 4, 2021 Author Share Posted January 4, 2021 Just now, repomanz said: No problem. Is there a way we can debug this? My new install completed including a fresh zoneminder app data directory and it comes up with no problem (except all my configurations / cameras are gone). Database issues are difficult. You might try the Zoneminder forums for some help. Quote Link to comment
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.