kikkawa

Hello! i went today to pull some footage from zoneminder however the web ui does not load, if i remove the /zm apache shows its running there are no updates so its on the latest version upon checking the logs i see the below error if i move the mysql folder from the appdata, then let it rebuild it again zm webui works however it does not have any config for the cameras,events, schedule etc it is still recording the events when i browse to the folders manually, however it would be nice to have the ui working again is there a way to repair the telemtry server via shell or file editing? cheers! Jan 24 19:11:08 0042f633213e syslog-ng[20]: syslog-ng starting up; version='3.25.1' Performing updates... Hit:1 http://archive.ubuntu.com/ubuntu focal InRelease Hit:2 http://archive.ubuntu.com/ubuntu focal-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu focal-backports InRelease Hit:4 http://ppa.launchpad.net/iconnor/zoneminder-1.36/ubuntu focal InRelease Hit:5 http://ppa.launchpad.net/ondrej/apache2/ubuntu focal InRelease Hit:6 http://ppa.launchpad.net/ondrej/php/ubuntu focal InRelease Hit:7 http://security.ubuntu.com/ubuntu focal-security InRelease Reading package lists... Reading package lists... Building dependency tree... Reading state information... Calculating upgrade... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Reading package lists... Building dependency tree... Reading state information... 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Using existing keys in "/config/keys" Using existing conf folder File zm.conf already copied File zmeventnotification.ini already moved File secrets.ini already moved Event notification server already moved Pushover api already moved Using existing ssmtp folder Using existing mysql database folder Copy /config/control/ scripts to /usr/share/perl5/ZoneMinder/Control/ Copy /config/conf/ scripts to /etc/zm/conf.d/ Creating symbolink links usermod: no changes usermod: no changes usermod: no changes Using existing data directory for events Using existing data directory for images Using existing data directory for temp Using existing data directory for cache Starting services... * Starting Apache httpd web server apache2 * * Stopping MariaDB database server mysqld ...done. * Starting MariaDB database server mysqld ...done. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[892]: Upgrading MySQL tables if necessary. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: Looking for 'mysql' as: /usr/bin/mysql Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: Looking for 'mysqlcheck' as: /usr/bin/mysqlcheck Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: This installation of MariaDB is already upgraded to 10.3.39-MariaDB. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: There is no need to run mysql_upgrade again for 10.3.39-MariaDB. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[898]: You can use --force if you still want to run mysql_upgrade Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[905]: Checking for insecure root accounts. Jan 24 19:11:22 0042f633213e /etc/mysql/debian-start[909]: Triggering myisam-recover for all MyISAM tables and aria-recover for all Aria tables Initiating database upgrade to version 1.36.35 from version 1.36.35 Upgrading database to version 1.36.35 Database upgrade to version 1.36.35 successful. Freshening configuration in database Migratings passwords, if any... Loading config from DB 227 entries Saving config to DB 227 entries Starting ZoneMinder: ZoneMinder started successfully Jan 24 19:11:35 0042f633213e cron[1043]: (CRON) INFO (pidfile fd = 3) Jan 24 19:11:35 0042f633213e cron[1043]: (CRON) INFO (Skipping @reboot jobs -- not system startup) Jan 24 19:11:36 0042f633213e zmtelemetry[1030]: WAR [Telemetry server returned HTTP POST error code: 301] Jan 24 19:11:36 0042f633213e zmc_m1[994]: WAR [zmc_m1] [Monitor dimensions are 2560x1440 but camera is sending 4608x1728] Jan 24 19:17:01 0042f633213e CRON[1061]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly)

Firstly love the docker for atm8 Thank you! I have one minor issue, even when allocating 8gb ram min and 16gb max, When i try to go into the Nether for the first time the server crashes with the following log Any ideas? crash-2023-03-12_13.34.43-server.txt

I can confirm i found 2 sticks of RAM that would not POST when they were installed solo on the system, these have been replaced and the system has been online for 2.5 days so far with no issues Thank you for you help itimpi!

Memtest does seem very broad and looks at the whole, says yeah everything looks good. Maybe if you ran each stick with memtest on an indivual basis (would take a long time) it *might* show some errors but for the sake of a few power downs and some clicking ram in, its eaiser to swap hardware You've been fantastic thank you!

Hi JorgeB, Thank you for taking a look at the logs for me and confirming my thoughts of cant find anything that indicates the reboot I've had the system running on a single 8GB stick overnight, its finishing a parity check before i play around it more I beleive one of the 8 8Gb sticks could have a fault that wasnt picked up by memtest, as so far it seems to be stable just with high ram usage! Ill add a second stick later on and look at replacing them as well

Hello Unraid Community! My server keeps randomly rebooting at random times, it happened a few weeks back ensured everything was up to date as when it rebooted it kept killing plex config xml which required a rebuild of the docker. Since then it was running 24/7 for around 3 weeks with no issues from what i could tell but it has restarted twice today one at 5am and then again around 11am (08/01/2023) When it happened first time memtest was ran for 8 hours, had no errors Bios is up to date and tried restoring default Tested psu and tried another one still rebooted Tested different ram still reboots Disabled all vms so they are not running, removed dockers that are no longer used and cleaned the app data I've attatched the diagnostics file and syslog, enabled syslog after the first rebooting ocurred but cant see the cause to the reboots Seems silly but i do have a wifi plug to monitor power usage but fail to see how this would cause it to reboot at all Im hopeing the more knowledgable people would be able to point in the direction of the faults tower-diagnostics-20230108-1234.zip syslog-192.168.200.137.log

Thank you for getting back to me, ill uncheck the cores and let unraid do its thing ive allocted 15gb for xms and 25gb for xmx which has helped a little, it is a very big mod pack so i know im asking a lot out of the server and docker its maily in one of the dimensions that things can crash

Im running a modded minecraft server on the docker, only 1 server running and when its just me playing its fine when player 2 joins it gets a little laggy despite being allocated 5gb xms to 15gb xmx ram, pack is ATM 6 so its about 300 mods Is there anything else to up the resources to give a smoother play? Changed the docker to use 8 cores and 8 threads out of the cpus available, would it be worth upping the allocated ram to 20gb+ in mine os server as well?

Thank you! You're an absolute legend changing from bridge to host fixed my adoption issue, it connected up instantly after switching!

Hello, I'm trying to get Filezilla to connect to swag (letsencrypt) they have config files for most apps but not for filezilla, i tried creating my own using the default sample ones but i get 502 bad gateway like its not being pointed in the right direction is there anything im missing at all? I can access it through my ddns web address tho so i know the ftp is working on the correct port ## Version 2021/05/18 # make sure that your dns has a cname set for <container_name> and that your <container_name> container is not using a base url server { listen 443 ssl; listen [::]:443 ssl; server_name filezilla.*; include /config/nginx/ssl.conf; client_max_body_size 0; # enable for ldap auth, fill in ldap details in ldap.conf #include /config/nginx/ldap.conf; # enable for Authelia #include /config/nginx/authelia-server.conf; location / { # enable the next two lines for http auth #auth_basic "Restricted"; #auth_basic_user_file /config/nginx/.htpasswd; # enable the next two lines for ldap auth #auth_request /auth; #error_page 401 =200 /ldaplogin; # enable for Authelia #include /config/nginx/authelia-location.conf; include /config/nginx/proxy.conf; include /config/nginx/resolver.conf; set $upstream_app filezilla; set $upstream_port 3000; set $upstream_proto https; proxy_pass $upstream_proto://$upstream_app:$upstream_port; } # location ~ (/filezilla)?/api { # include /config/nginx/proxy.conf; # include /config/nginx/resolver.conf; # set $upstream_app filezilla; # set $upstream_port 3000; # set $upstream_proto https; # proxy_pass $upstream_proto://$upstream_app:$upstream_port; # # } }