March 11, 20242 yr On 3/9/2024 at 1:08 PM, snowmirage said: I think my nzbgetvpn container may have stopped working sometime ago. I got back to doing some upgrades to my home lab. I've setup Unraid with multiple VLANs. I've just moved all my docker containers to one of the new VLANS. "Network br2.2" I can't seem to access the nzbget web ui. When I look at the logs 2024-03-09 12:57:09,145 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '25361' 2024-03-09 12:57:39,435 DEBG 'watchdog-script' stdout output: [info] nzbget not running 2024-03-09 12:57:39,435 DEBG 'watchdog-script' stdout output: [info] Nzbget config file already exists, skipping copy 2024-03-09 12:57:39,447 DEBG 'watchdog-script' stdout output: [info] Attempting to start nzbget... 2024-03-09 12:57:39,456 DEBG 'watchdog-script' stdout output: [info] Nzbget process started [info] Waiting for Nzbget process to start listening on port 6789... 2024-03-09 12:57:39,460 DEBG 'watchdog-script' stdout output: [info] Nzbget process is listening on port 6789 The service seems to be listening on the port. and I did update the LAN_NETWORK variable and added all my local networks. I can ping the docker containers IP address (10.2.0.73) and get a response but I get no response at all when trying to access the webgui. Looking at wireshark, when I try to connect to the webui there's not return traffic at all from the container. Any ideas what might be wrong here? Well... I think I fixed it... but I haven't a clue how... I change the docker container from the above network type to give it an IP address on my VLAN interface (br2.2) to the "Bridge" network type. after doing this The UI reports the container has an IP of 172. something.... I have nothing on my network or unraid server using that IP range to my knowledge.... But I happen to try putting in the IP address of my unraid server and the nzbget port in the browser and ... there it is working at 10.2.0.16:6789... No idea what that did or how its working unfortunately ...
May 1, 20242 yr FYI in the latest MySQL image the mysql native password starts up disabled, and `--default-authentication-plugin=mysql_native_password` does not work. If you're having issues connecting, try adding to the post arguments (advanced mode) `--mysql-native-password=ON`.
May 1, 20242 yr 44 minutes ago, BoxOfSnoo said: FYI in the latest MySQL image the mysql native password starts up disabled, and `--default-authentication-plugin=mysql_native_password` does not work. If you're having issues connecting, try adding to the post arguments (advanced mode) `--mysql-native-password=ON`. Thanks for sharing; I had a few things that it evidently borked, invoice ninja, that I hadn't had time to hunt down. No telling what who or how I setup Invoice Ninja that way...sigh LOL
May 1, 20242 yr I wonder if they're going to roll back or what their intentions are/were here? I have a few things I can't get to work even with that argument added - can't remember how I have what setup so I am sure it's a skill issue. Can't downgrade MySWQL Container though can I?
May 7, 20242 yr On 5/1/2024 at 2:58 PM, BoxOfSnoo said: FYI in the latest MySQL image the mysql native password starts up disabled, and `--default-authentication-plugin=mysql_native_password` does not work. If you're having issues connecting, try adding to the post arguments (advanced mode) `--mysql-native-password=ON`. From the Log file---- @Bungy, Any thoughts?
May 8, 20242 yr On 5/1/2024 at 4:01 PM, blaine07 said: I can't get to work even with that argument added - can't remember how I have what setup so I am sure it's a skill issue. Luckily, in my case, I found the MYSQL_USER name and the MYSQL_PASSWORD in plain text in the KODI .xml file which made it possible to regain access to the stored MYSQL database. But I don't can't find (or remember) what the MYSQL_ROOT_PASSWORD password was. So there is no way for me to get into MYSQL to run any commands that would allow me to change how the password is hashed...
July 9, 20242 yr So, this has been 2 full months... but there's a way... I found one article on StackOverflow: https://stackoverflow.com/questions/48249912/change-mysql-password-in-docker-container However, note that the newest docker image is MySQL 9.0 and the parameter/option is not longer deprecated but totally unsupported. You'll have to run some scripts to update passwords to the newer format... I don't have the reference on hand for that ATM... Edit: ...ok, found something: https://dba.stackexchange.com/questions/330384/how-do-i-change-the-authentication-plugin-for-users-mysql-sys-mysql-session-et Edited July 9, 20242 yr by BoxOfSnoo Added link
July 10, 20242 yr 23 hours ago, BoxOfSnoo said: So, this has been 2 full months... but there's a way... I found one article on StackOverflow: https://stackoverflow.com/questions/48249912/change-mysql-password-in-docker-container However, note that the newest docker image is MySQL 9.0 and the parameter/option is not longer deprecated but totally unsupported. You'll have to run some scripts to update passwords to the newer format... I don't have the reference on hand for that ATM... Edit: ...ok, found something: https://dba.stackexchange.com/questions/330384/how-do-i-change-the-authentication-plugin-for-users-mysql-sys-mysql-session-et Care to go step by step on how?! I can't seven use the command "mysql -uroot..." etc...
July 10, 20242 yr I attempted to upgrade an existing mysql docker and got this... MySQL Server - end. 2024-07-10T21:59:41.828156Z 0 [System] [MY-015015] [Server] MySQL Server - start. 2024-07-10T21:59:42.074860Z 0 [System] [MY-010116] [Server] /usr/sbin/mysqld (mysqld 9.0.0) starting as process 1 2024-07-10T21:59:42.093831Z 1 [System] [MY-013576] [InnoDB] InnoDB initialization has started. 2024-07-10T21:59:42.575433Z 1 [System] [MY-013577] [InnoDB] InnoDB initialization has ended. 2024-07-10T21:59:42.584731Z 1 [ERROR] [MY-014060] [Server] Invalid MySQL server upgrade: Cannot upgrade from 80300 to 90000. Upgrade to next major version is only allowed from the last LTS release, which version 80300 is not. It's now just repeats this every time I try and start mysql. Not sure how to recover from this. Can't get to console.
August 3, 20241 yr @Saiba Samurai While I'm not certain of the easiest way to upgrade to 9.0, you can force the container back to 8.3 by editing the container and setting the 'Repository' tag to 'mysql:8.3.0'. Save the changes and it will refresh the container with your previous version of MySQL and should fire right up. Edited August 3, 20241 yr by Josh208
September 24, 20241 yr I am utilizing the nzbget docker and am having some issues. Until recently everything was working fine, but now for some reason I cannot get my downloaders to talk to nzbget nor can I get the web interface to come up. I have verified the logs and everything looks ok to me, I don't see any errors in fact I see everything saying it is fine. What am I missing and what do I need to do to get this back in a functioning state. The latest log is below - I have redacted some information. Created by... ___. .__ .__ \_ |__ |__| ____ | |__ ____ ___ ___ | __ \| |/ \| | \_/ __ \\ \/ / | \_\ \ | | \ Y \ ___/ > < |___ /__|___| /___| /\___ >__/\_ \ \/ \/ \/ \/ \/ https://hub.docker.com/u/binhex/ 2024-09-24 08:52:46.966377 [info] Host is running unRAID 2024-09-24 08:52:46.979750 [info] System information Linux e1c8900cdf73 6.1.64-Unraid #1 SMP PREEMPT_DYNAMIC Wed Nov 29 12:48:16 PST 2023 x86_64 GNU/Linux 2024-09-24 08:52:47.008022 [info] OS_ARCH defined as 'x86-64' 2024-09-24 08:52:47.025277 [warn] PUID not defined (via -e PUID), defaulting to '99' 2024-09-24 08:52:48.959272 [warn] PGID not defined (via -e PGID), defaulting to '100' 2024-09-24 08:52:50.828624 [warn] UMASK not defined (via -e UMASK), defaulting to '000' 2024-09-24 08:52:50.844165 [info] Permissions already set for '/config' 2024-09-24 08:52:50.876647 [info] Deleting files in /tmp (non recursive)... 2024-09-24 08:52:50.898736 [info] VPN_ENABLED defined as 'yes' 2024-09-24 08:52:50.915896 [warn] VPN_CLIENT not defined (via -e VPN_CLIENT), defaulting to 'openvpn' 2024-09-24 08:52:50.931601 [info] VPN_PROV defined as 'pia' 2024-09-24 08:52:51.564830 [info] OpenVPN config file (ovpn extension) is located at /config/openvpn/mexico.ovpn 2024-09-24 08:52:51.617485 [info] VPN remote server(s) defined as 'mexico.privacy.network,' 2024-09-24 08:52:51.632153 [info] VPN remote port(s) defined as '1198,' 2024-09-24 08:52:51.646987 [info] VPN remote protcol(s) defined as 'udp,' 2024-09-24 08:52:51.663793 [info] VPN_DEVICE_TYPE defined as 'tun0' 2024-09-24 08:52:51.681479 [info] VPN_OPTIONS not defined (via -e VPN_OPTIONS) 2024-09-24 08:52:51.697934 [info] LAN_NETWORK defined as '192.168.0.0/24' 2024-09-24 08:52:51.714384 [info] NAME_SERVERS defined as '8.8.8.8,1.1.1.1' 2024-09-24 08:52:51.731640 [info] VPN_USER defined as '**********' 2024-09-24 08:52:51.747720 [info] VPN_PASS defined as '**********' 2024-09-24 08:52:51.764920 [warn] STRICT_PORT_FORWARD not defined (via -e STRICT_PORT_FORWARD), defaulting to 'yes' 2024-09-24 08:52:51.782292 [warn] ENABLE_PRIVOXY not defined (via -e ENABLE_PRIVOXY), defaulting to 'no' 2024-09-24 08:52:51.801546 [info] VPN_INPUT_PORTS not defined (via -e VPN_INPUT_PORTS), skipping allow for custom incoming ports 2024-09-24 08:52:51.819028 [info] VPN_OUTPUT_PORTS not defined (via -e VPN_OUTPUT_PORTS), skipping allow for custom outgoing ports 2024-09-24 08:52:51.837899 [info] Starting Supervisor... 2024-09-24 08:52:52,140 INFO Included extra file "/etc/supervisor/conf.d/nzbget.conf" during parsing 2024-09-24 08:52:52,140 INFO Set uid to user 0 succeeded 2024-09-24 08:52:52,141 INFO supervisord started with pid 7 2024-09-24 08:52:53,144 INFO spawned: 'shutdown-script' with pid 180 2024-09-24 08:52:53,145 INFO spawned: 'start-script' with pid 181 2024-09-24 08:52:53,146 INFO spawned: 'watchdog-script' with pid 182 2024-09-24 08:52:53,147 INFO reaped unknown pid 8 (exit status 0) 2024-09-24 08:52:53,150 DEBG 'start-script' stdout output: [info] VPN is enabled, beginning configuration of VPN 2024-09-24 08:52:53,150 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-09-24 08:52:53,150 INFO success: start-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-09-24 08:52:53,151 INFO success: watchdog-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 2024-09-24 08:52:53,193 DEBG 'start-script' stdout output: [info] Adding 8.8.8.8 to /etc/resolv.conf 2024-09-24 08:52:53,196 DEBG 'start-script' stdout output: [info] Adding 1.1.1.1 to /etc/resolv.conf 2024-09-24 08:52:53,368 DEBG 'start-script' stdout output: [info] Default route for container is 192.168.0.254 2024-09-24 08:52:53,378 DEBG 'start-script' stdout output: [info] Docker network defined as 192.168.0.0/24 2024-09-24 08:52:53,381 DEBG 'start-script' stdout output: [info] Adding 192.168.0.0/24 as route via docker eth0 2024-09-24 08:52:53,382 DEBG 'start-script' stderr output: RTNETLINK answers: File exists 2024-09-24 08:52:53,382 DEBG 'start-script' stdout output: [info] ip route defined as follows... -------------------- 2024-09-24 08:52:53,382 DEBG 'start-script' stdout output: default via 192.168.0.254 dev eth0 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.13 2024-09-24 08:52:53,383 DEBG 'start-script' stdout output: -------------------- 2024-09-24 08:52:53,386 DEBG 'start-script' stdout output: iptable_mangle 16384 1 ip_tables 28672 3 iptable_filter,iptable_nat,iptable_mangle x_tables 45056 16 ip6table_filter,xt_conntrack,iptable_filter,ip6table_nat,xt_tcpudp,xt_addrtype,xt_CHECKSUM,xt_nat,ip6_tables,ipt_REJECT,ip_tables,iptable_nat,ip6table_mangle,xt_MASQUERADE,iptable_mangle,xt_mark 2024-09-24 08:52:53,386 DEBG 'start-script' stdout output: [info] iptable_mangle support detected, adding fwmark for tables 2024-09-24 08:52:53,516 DEBG 'start-script' stdout output: [info] iptables defined as follows... -------------------- 2024-09-24 08:52:53,517 DEBG 'start-script' stdout output: -P INPUT DROP -P FORWARD DROP -P OUTPUT DROP -A INPUT -s 192.168.0.0/24 -d 192.168.0.0/24 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p udp -m udp --sport 1198 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --dport 6789 -j ACCEPT -A INPUT -i eth0 -p tcp -m tcp --sport 6789 -j ACCEPT -A INPUT -p icmp -m icmp --icmp-type 0 -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -i tun0 -j ACCEPT -A OUTPUT -s 192.168.0.0/24 -d 192.168.0.0/24 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p udp -m udp --dport 1198 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --dport 6789 -j ACCEPT -A OUTPUT -o eth0 -p tcp -m tcp --sport 6789 -j ACCEPT -A OUTPUT -p icmp -m icmp --icmp-type 8 -j ACCEPT -A OUTPUT -o lo -j ACCEPT -A OUTPUT -o tun0 -j ACCEPT 2024-09-24 08:52:53,518 DEBG 'start-script' stdout output: -------------------- 2024-09-24 08:52:53,519 DEBG 'start-script' stdout output: [info] Starting OpenVPN (non daemonised)... 2024-09-24 08:52:53,650 DEBG 'start-script' stdout output: 2024-09-24 08:52:53 DEPRECATED OPTION: --cipher set to 'aes-128-cbc' but missing in --data-ciphers (AES-256-GCM:AES-128-GCM). Future OpenVPN version will ignore --cipher for cipher negotiations. Add 'aes-128-cbc' to --data-ciphers or change --cipher 'aes-128-cbc' to --data-ciphers-fallback 'aes-128-cbc' to silence this warning. 2024-09-24 08:52:53,650 DEBG 'start-script' stdout output: 2024-09-24 08:52:53 WARNING: file 'credentials.conf' is group or others accessible 2024-09-24 08:52:53 OpenVPN 2.5.4 [git:makepkg/3f7a85b9aebe7be0+] x86_64-pc-linux-gnu [SSL (OpenSSL)] [LZO] [LZ4] [EPOLL] [PKCS11] [MH/PKTINFO] [AEAD] built on Oct 5 2021 2024-09-24 08:52:53 library versions: OpenSSL 1.1.1l 24 Aug 2021, LZO 2.10 2024-09-24 08:52:53,650 DEBG 'start-script' stdout output: 2024-09-24 08:52:53 NOTE: the current --script-security setting may allow this configuration to call user-defined scripts 2024-09-24 08:52:53,651 DEBG 'start-script' stdout output: 2024-09-24 08:52:53 CRL: loaded 1 CRLs from file -----BEGIN X509 CRL----- XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX -----END X509 CRL----- 2024-09-24 08:52:53,651 DEBG 'start-script' stdout output: 2024-09-24 08:52:53 TCP/UDP: Preserving recently used remote address: [AF_INET]*.*.*.89:1198 2024-09-24 08:52:53 UDP link local: (not bound) 2024-09-24 08:52:53 UDP link remote: [AF_INET]*.*.*.89:1198 2024-09-24 08:52:53,910 DEBG 'start-script' stdout output: 2024-09-24 08:52:53 [mexico408] Peer Connection Initiated with [AF_INET]*.*.*.89:1198 2024-09-24 08:52:53,980 DEBG 'start-script' stdout output: 2024-09-24 08:52:53 TUN/TAP device tun0 opened 2024-09-24 08:52:53 net_iface_mtu_set: mtu 1500 for tun0 2024-09-24 08:52:53 net_iface_up: set tun0 up 2024-09-24 08:52:53,981 DEBG 'start-script' stdout output: 2024-09-24 08:52:53 net_addr_v4_add: 10.14.112.45/24 dev tun0 2024-09-24 08:52:53 /root/openvpnup.sh tun0 1500 1553 10.14.112.45 255.255.255.0 init 2024-09-24 08:52:53,982 DEBG 'start-script' stdout output: 2024-09-24 08:52:53 Initialization Sequence Completed 2024-09-24 08:53:01,102 DEBG 'start-script' stdout output: [info] Attempting to get external IP using 'http://checkip.amazonaws.com'... 2024-09-24 08:53:01,428 DEBG 'start-script' stdout output: [info] Successfully retrieved external IP address *.*.*.89 2024-09-24 08:53:01,428 DEBG 'start-script' stdout output: [info] Script started to assign incoming port 2024-09-24 08:53:01,428 DEBG 'start-script' stdout output: [info] Port forwarding is enabled [info] Checking endpoint 'mexico.privacy.network' is port forward enabled... 2024-09-24 08:53:02,385 DEBG 'start-script' stdout output: [info] PIA endpoint 'mexico.privacy.network' is in the list of endpoints that support port forwarding 2024-09-24 08:53:02,385 DEBG 'start-script' stdout output: [info] List of PIA endpoints that support port forwarding:- 2024-09-24 08:53:02,386 DEBG 'start-script' stdout output: [info] ua.privacy.network [info] slovenia.privacy.network [info] za.privacy.network [info] mk.privacy.network [info] dz.privacy.network [info] mongolia.privacy.network [info] ca-montreal.privacy.network [info] morocco.privacy.network [info] sweden.privacy.network [info] saudiarabia.privacy.network [info] au-sydney.privacy.network [info] yerevan.privacy.network [info] aus-melbourne.privacy.network [info] au-adelaide-pf.privacy.network [info] es-valencia.privacy.network 2024-09-24 08:53:02,386 DEBG 'start-script' stdout output: [info] panama.privacy.network [info] malta.privacy.network [info] de-germany-so.privacy.network [info] sweden-2.privacy.network [info] ae.privacy.network [info] ca-vancouver.privacy.network [info] aus-perth.privacy.network [info] sg.privacy.network [info] japan.privacy.network [info] ca-toronto.privacy.network [info] br.privacy.network [info] ireland.privacy.network [info] italy-2.privacy.network [info] man.privacy.network [info] brussels.privacy.network [info] lt.privacy.network [info] uk-2.privacy.network [info] uk-southampton.privacy.network [info] sofia.privacy.network [info] santiago.privacy.network [info] al.privacy.network [info] france.privacy.network [info] gt-guatemala-pf.privacy.network [info] pt.privacy.network [info] montenegro.privacy.network [info] ar.privacy.network [info] israel.privacy.network [info] ro.privacy.network [info] taiwan.privacy.network [info] vietnam.privacy.network [info] kualalumpur.privacy.network [info] swiss.privacy.network [info] kazakhstan.privacy.network [info] de-frankfurt.privacy.network [info] fi.privacy.network [info] jakarta.privacy.network [info] uy-uruguay-pf.privacy.network [info] hk.privacy.network 2024-09-24 08:53:02,386 DEBG 'start-script' stdout output: [info] ad.privacy.network [info] ca-ontario.privacy.network [info] qatar.privacy.network [info] poland.privacy.network [info] liechtenstein.privacy.network [info] mexico.privacy.network [info] italy.privacy.network [info] ba.privacy.network [info] kr-south-korea-pf.privacy.network [info] au-australia-so.privacy.network [info] georgia.privacy.network [info] bahamas.privacy.network [info] spain.privacy.network [info] egypt.privacy.network [info] de-berlin.privacy.network [info] bangladesh.privacy.network [info] no.privacy.network [info] srilanka.privacy.network [info] denmark.privacy.network [info] au-brisbane-pf.privacy.network [info] gr.privacy.network [info] greenland.privacy.network [info] fi-2.privacy.network [info] macau.privacy.network [info] sk.privacy.network [info] venezuela.privacy.network [info] nl-netherlands-so.privacy.network [info] ca-ontario-so.privacy.network [info] cyprus.privacy.network [info] cambodia.privacy.network [info] ee.privacy.network [info] philippines.privacy.network [info] is.privacy.network [info] sanjose.privacy.network [info] bo-bolivia-pf.privacy.network 2024-09-24 08:53:02,386 DEBG 'start-script' stdout output: [info] np-nepal-pf.privacy.network [info] japan-2.privacy.network [info] uk-manchester.privacy.network [info] hungary.privacy.network [info] ec-ecuador-pf.privacy.network [info] rs.privacy.network [info] denmark-2.privacy.network [info] china.privacy.network [info] bogota.privacy.network [info] tr.privacy.network [info] uk-london.privacy.network [info] austria.privacy.network [info] nigeria.privacy.network [info] in.privacy.network [info] nz.privacy.network [info] lv.privacy.network [info] pe-peru-pf.privacy.network [info] monaco.privacy.network [info] zagreb.privacy.network [info] nl-amsterdam.privacy.network [info] lu.privacy.network [info] czech.privacy.network [info] md.privacy.network 2024-09-24 08:53:04,783 DEBG 'start-script' stdout output: [info] Successfully assigned and bound incoming port '27425' 2024-09-24 08:53:05,194 DEBG 'watchdog-script' stdout output: [info] nzbget not running 2024-09-24 08:53:05,195 DEBG 'watchdog-script' stdout output: [info] Nzbget config file already exists, skipping copy 2024-09-24 08:53:05,215 DEBG 'watchdog-script' stdout output: [info] Attempting to start nzbget... 2024-09-24 08:53:05,276 DEBG 'watchdog-script' stdout output: [info] Nzbget process started [info] Waiting for Nzbget process to start listening on port 6789... 2024-09-24 08:53:05,279 DEBG 'watchdog-script' stdout output: [info] Nzbget process is listening on port 6789
September 29, 20241 yr The PostgreSQL container is v15 and lasted updated a year ago, but I notice v17 launched this month. Is this still a recommended container? If not, which one is a better option?
October 1, 20241 yr I just updated today and now it no longer can connect to my servers. Worked before the upgrade. Anyone else having this issue? I see nothing odd in the log file. Website works, etc, but when I try to download anything it just fails. I don't see any details in the log file. Can someone point me to a better log than supervisord.log?
November 21, 20241 yr I noticed that my mysql container is not working. All servers and systems cannot access. phpmyadmin cannot login. When in the container, trying "mysql status" returns: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) I've been hunting around inside the container, and can find no logs, because it appears that the main mysql process will not start. I'm not sure how this could suddenly happen, nothing changed in my configuration. Anyhow, I've tried chown on the directory /var/run/mysqld and /var/lib/mysql I tried to create the sock file manually, that produces no good results just another similar error. Tried creating a new symlink, that results in an error "cannot access '/var/run/mysqld/mysqld.sock': Too many levels of symbolic links" Tried deleting and recreating the contaner. Tried updating to latest (I was using 9.0.1 and updated to 9.1.0. I'm unsure how to install any tools in this distro, yum and dmf seem to be missing. I'm pretty stuck at this point, googling and trying to understand. Can anyone help?
December 15, 20241 yr On 11/21/2024 at 4:11 AM, KptnKMan said: I noticed that my mysql container is not working. All servers and systems cannot access. phpmyadmin cannot login. When in the container, trying "mysql status" returns: ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) I've been hunting around inside the container, and can find no logs, because it appears that the main mysql process will not start. I'm not sure how this could suddenly happen, nothing changed in my configuration. Anyhow, I've tried chown on the directory /var/run/mysqld and /var/lib/mysql I tried to create the sock file manually, that produces no good results just another similar error. Tried creating a new symlink, that results in an error "cannot access '/var/run/mysqld/mysqld.sock': Too many levels of symbolic links" Tried deleting and recreating the contaner. Tried updating to latest (I was using 9.0.1 and updated to 9.1.0. I'm unsure how to install any tools in this distro, yum and dmf seem to be missing. I'm pretty stuck at this point, googling and trying to understand. Can anyone help? A post above noted that people may be having issues with version 9.0+ You can try rolling back to 8.3.0, that worked for me Another reference here: https://www.reddit.com/r/unRAID/comments/1du4yht/alert_mysql_latest_tag_changed_today_to_9xx/
May 21, 20251 yr OpenProject 16 requires PostgreSQL 16 now. This is the message being shown to users of OpenProject 16 that released a few hours ago:Starting with OpenProject 16.0, PostgreSQL 16 is required to use OpenProject. Your installation will remain functional with your current database, but anticipate incompatability in future releases.
September 22, 2025Sep 22 The nzbgetvpn docker from jshridha is now 17 months old. Any chance that it gets updated / switched to a newer docker image?
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.