phreeq

I'll see about kicking that device off the network for the next couple of days to see if it resolves things. I know what it is, but I'll have to figure out later why it's spamming so hard, it won't kill me to kick it off for a few days for testing.

This is the most recent syslog file I was able to grab before having to go to work syslog-192.168.1.15.log

I'm lost, any chance someone can help me see what might be wrong here? phreeq-unraid-diagnostics-20260913-1343.zip

Well, I looked just now after a restart, and it seems that I did have syslog server set up. I'll take a look and see if I can figure anything out and report back if I'm too dumb to understand.

Earlier this week, I woke up to find that my server had crashed during the night and was completely unresponsive. Not having time due to work, I simply restarted the machine and headed out for the day. Server was fine for the day, but crashed again that night, only to be noticed the next morning. I shut it down and decided to look into it this weekend. Yesterday, since it hadn't been done in a while and I noticed the fans were spinning pretty high earlier in the week, I opened the case up and carefully blew out any dust buildup in the machine. Upon restarting, the system came up with no issues, other than wanting to run a parity check. Having too much planned for the day, I left it to do it's parity check and went about my business. It crashed again last night. I'm again sitting in a place where my fans are pegged at 100%, I can't access the web interface, and I can't ssh into the machine, so I can't pull any diagnostics to see what the hell happened.

I'm using binhex/arch-urbackup:2.5.33-2-01

I went and pulled version 2.5.33-2-01, which is admittedly an old version, and it's running now. I'll keep an eye on the repository and see if a new update rolls out that may fix this issue.

I'm having the same issue

After completing the parity check from the last startup, I pulled the USB drive and ran a check with Disk Utility. It didn't find any problems, so I'm guessing that the USB drive isn't the source of the problem.

The system may have been semi-crashed when I grabbed the last set of diagnostics, but this should be a good set. phreeq-unraid-diagnostics-20240421-0854.zip

I'm getting invalid option f

It all started with a drive failure. I had a drive fail, so I replaced it and rebuilt onto a new, bigger, drive. Once the rebuild was finished, somehow all of my docker containers were gone. Now, when I reinstall the container, and try to restore from app data backups, sometimes my GUI will go completely white, not even the menu bar is left. tower-diagnostics-20240420-1025.zip

Just a note if anyone runs into the problem I just had. I'm using postgresql for my database and when I updated the wikijs docker yesterday it broke. I didn't make a full note of the error I was getting, but part of it was ENOTFOUND undefined:undefined. Following instructions I can't find anymore for setting it up originally, my db section of the config.yml read: db: type: postgres # PostgreSQL / MySQL / MariaDB / MS SQL Server only: host: Postgres12.5 port: 5432 user: root pass: root db: wikijs ssl: false This was working for quite a while for me, but all of a sudden it didn't. I found that changing the host from the hostname of the postgres docker to the IP address fixed it for me.

Thanks for this, not sure if I just missed it when I tried it, or if it didn't work for me then. I'll give it another go in a little bit to see if I screwed up, which is ALWAYS possible. EDIT: Okay, the answer is I screwed up. I just tried it again and it did work. The only thing I can think of is, I was trying to use it behind SWAG and maybe I couldn't register the first account when processing through SWAG, but this time I did it from the local IP of my server. I set up the first account, then tested accessing through SWAG, and I was able to log in and all looks good. Now, I just need to dig in and figure out how to use the system. Thanks @Marzel!