pmcnano

Did you find a solution for this? It started happening every week or so to me. There's nothing in the logs that can tell me something, but because of the time of the day this happens it's clear it's happening when the docker container updates. Like you said, a restart fixes the issue. The funny thing is, I know it's not issolated. Literally when it happens to me, all the servers shared to me are also down, and I have contacted the owners, and they see the same issues. I'm surprised I can't find more reports for this issue.

Negative on my end. Not using Frigate.

Well, I ended up recreating my docker.img. Reinstalled everything and I think there might've been one container causing issues so I just turned that one off. That being said I didn't have enough time to really check. Also before I started the high CPU usage was there even with all containers stopped. I also found some similar posts in the forum, so I'm going to say there's something off.

I'm experiencing this as well. Did you figure something out? Stopping every single docker container does not help at all. Edit: Seems like my docker image got corrupted? I createad a new one and I'm resintalling everything and seems to be okay. Edit2: Now that I've reinstalled everything, seems to be back to the same thing, not as bad but 80% CPU usage now.

I was just looking for something like this. Thanks! That being said, your unraid template is missing somethings...I will try to fix it and submit a PR to your repo. Edit: It's actually all okay, the thing is, and I'm not sure how to fix, since the ports are not specified, the docker app doesn't offer to open the web gui. But just going to the port 8090 works fine. Probably worth allowing the user to specify which port is going to use. And I thiiink maybe the app icon has to be PNG but not entirely sure. Edit2: Seems like the database is reset after restarting the container? I assume is because it's not being stored in the appdata. Edit3: Sorry for all the edits. Added a path mapping, /app/pb_data to my appdata folder and the database is now persisted.

Submitted a PR to fix your Muse template. Though even if it now runs, it still doesn't work while trying to play some media.

Just as an FYI, this image gave me the answer: I don't recall ever moving my docker "Host access to custom networks" setting, but it's enabled. I have a feeling it was auto-enabled at some point by an update or something else. And per that table, it won't work with NAT = true. Since I didn't want to stop all my docker containers, I went with the last option, and added my static routes with NAT= false and my problems were solved.

@CorneliousJD any reason to require a redis password? What if my redis instance has no password? 🤔

@ich777idk if you noticed, nor if it's normal. But the Craftopia docker seems to be using a lot of CPU all the time? Even with no activity?

balls, thanks! edit: pff, a vm won't do either, it requires a GPU for some reason.

Hey! Do you mind making a craftopia server? 🥺 Thanks for your work!

Hey @ich777 thanks for your apps! I tried looking for any repo I could just push a fix for this but couldn't find it. Either way, your mindustry "app" says the following: CONSOLE: To connect to the console open up the terminal for this docker and type in: 'docker exec -u terraria -ti NAMEOFYOURCONTAINER screen -xS Mindustry' (without quotes). The user is "mindustry" actually.

Ah, thanks! You are right. Tho, the last post does mention it works fine with sqlite, which is what we are using, no? Edit: Tried with postgres and same thing, also commented on that post. I also found a post saying it might be permission issues with the data directory, but they seem to be root already. I will keep an eye on that issue. Thanks!

@FoxxMD noticed that every time the docker restarts, it restarts the setup. You just complete it and your data is still there, but if I don't go there, the app doesn't run. For instance, if I restart my server, the slack notifications are down until I complete the setup again.

Yup, it does suck a bit, something changed and my database got corrupted with the update a week ago, I Spent days trying to fix it and reinstalling didn't work either. Ended up doing above. I feel like @SpaceInvaderOne missed something in the update but I don't think he has connected in a while. We'll see, I had to setup my cameras again but I have it all working again.

Since the update last night I am getting an error, I tried what @SpaceInvaderOne suggested for another problem a couple of replies before, but it didn't work. I removed the template and reinstalled, same error. 2020-05-14 17:06:31 11 [ERROR] mysqld: Incorrect information in file: './ccio/Presets.frm' Error: ER_NOT_FORM_FILE: Incorrect information in file: './ccio/Presets.frm' at Query.Sequence._packetToError (/opt/shinobi/node_modules/mysql/lib/protocol/sequences/Sequence.js:47:14) at Query.ErrorPacket (/opt/shinobi/node_modules/mysql/lib/protocol/sequences/Query.js:79:18) at Protocol._parsePacket (/opt/shinobi/node_modules/mysql/lib/protocol/Protocol.js:291:23) at Parser._parsePacket (/opt/shinobi/node_modules/mysql/lib/protocol/Parser.js:433:10) at Parser.write (/opt/shinobi/node_modules/mysql/lib/protocol/Parser.js:43:10) at Protocol.write (/opt/shinobi/node_modules/mysql/lib/protocol/Protocol.js:38:16) at Socket.<anonymous> (/opt/shinobi/node_modules/mysql/lib/Connection.js:88:28) at Socket.<anonymous> (/opt/shinobi/node_modules/mysql/lib/Connection.js:526:10) at Socket.emit (events.js:223:5) at addChunk (_stream_readable.js:309:12) at readableAddChunk (_stream_readable.js:290:11) at Socket.Readable.push (_stream_readable.js:224:10) at TCP.onStreamRead (internal/stream_base_commons.js:181:23) -------------------- at Protocol._enqueue (/opt/shinobi/node_modules/mysql/lib/protocol/Protocol.js:144:48) at Connection.query (/opt/shinobi/node_modules/mysql/lib/Connection.js:198:25) at /opt/shinobi/node_modules/knex/lib/dialects/mysql/index.js:130:18 at Promise._execute (/opt/shinobi/node_modules/bluebird/js/release/debuggability.js:384:9) at Promise._resolveFromExecutor (/opt/shinobi/node_modules/bluebird/js/release/promise.js:518:18) at new Promise (/opt/shinobi/node_modules/bluebird/js/release/promise.js:103:10) at Client_MySQL._query (/opt/shinobi/node_modules/knex/lib/dialects/mysql/index.js:124:12) at Client_MySQL.query (/opt/shinobi/node_modules/knex/lib/client.js:158:17) at Runner.query (/opt/shinobi/node_modules/knex/lib/runner.js:135:36) at /opt/shinobi/node_modules/knex/lib/runner.js:39:23 at tryCatcher (/opt/shinobi/node_modules/bluebird/js/release/util.js:16:23) at /opt/shinobi/node_modules/bluebird/js/release/using.js:185:26 at tryCatcher (/opt/shinobi/node_modules/bluebird/js/release/util.js:16:23) at Promise._settlePromiseFromHandler (/opt/shinobi/node_modules/bluebird/js/release/promise.js:547:31) at Promise._settlePromise (/opt/shinobi/node_modules/bluebird/js/release/promise.js:604:18) at Promise._settlePromise0 (/opt/shinobi/node_modules/bluebird/js/release/promise.js:649:10) { code: 'ER_NOT_FORM_FILE', errno: 1033, sqlMessage: "Incorrect information in file: './ccio/Presets.frm'", sqlState: 'HY000', index: 0, sql: 'ALTER TABLE `Presets` CHANGE COLUMN `type` `type` VARCHAR(50) NULL DEFAULT NULL AFTER `details`;' } !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! This Install of Shinobi is NOT Activated !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2020-05-14T17:06:33-05:00 This Install of Shinobi is NOT Activated

I wasn't on my computer when I replied a couple of minutes ago, but just in case:

I'm sorry but it actually works for me. I just checked both my tunnels and they are detected a open.

Not what I meant. To actually check that the port is in fact open. https://check-host.net/check-udp

Honestly, I don't see this has been mentioned. But have you checked that the UDP port is opened?

Did you figure this out?

Here

Awesome! Thanks. Ps. Did you read my reply with new information some posts back?

Hey, so, disabled my bond, I actually just used eth0. Briding enabled only for eth0 too. Same thing happened, I tried grabbing diagnostics, but it said (https://share.getcloudapp.com/WnuE0Ljd): Starting diagnostics collection... I waited for 40 minutes and nothing, just more kernel panics in the logs. Here are the logs (pastebin as it's pretty large, same KP over and over again as far as I can tell): https://pastebin.com/gQd8P7Zt Thanks! edit: I created a new diagnostics set, from console after the restart and it took 5 seconds, so yeah. Attaching it in case it helps with anything. tower-diagnostics-20200105-1932.zip

I will try that, question tho, how would I get the diagnostics before, if I can't access it? Thanks!