D'n'S137
-
Posts
33 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by D'n'S137
-
-
Dec 4 22:22:52 MPS kernel: mce: [Hardware Error]: Machine check events logged
Dec 4 22:22:52 MPS kernel: mce: [Hardware Error]: CPU 1: Machine Check: 0 Bank 5: bea0000000000108
Dec 4 22:22:52 MPS kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff8114fef2 MISC d012000100000000 SYND 4d000000 IPID 500b000000000
Dec 4 22:22:52 MPS kernel: mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1607116951 SOCKET 0 APIC 2 microcode 8001138
Dec 4 22:22:52 MPS kernel: #2 #3 #4 #5 #6 #7 #8 #9 #10 #11 #12 #13 #14 #15 -
Hello everyone,
Im Runnig Unraid 6.8.3 on an AMD RYZEN 7 1700 with 4x2TB HARD Drives(1Parity) and 2xSSDs(for Cache) 1SSD is 128GB and the other one is 256GB.
For Memory i have 32GB of DDR3 2144MHz RAM non ECC.
The Mainboard is a Gigabity B450 AORUS ELITE. (works like a charm)
For the GPU i got an old EVGA GTX 980TI Hybrid and an MSI GTX 710.
Plugins:
- Nerdpack
- ZFS(not in use)
- NVIDIA UNRAID(not in use)
- DenyHosts
- userScripts
- upnp-monitor
- fix-common-problems
- parity-check-tuning
- gui-links(not in use)
- dynamixsystemtemp
- dynamixCacheDirs
- dynamixActiveStreams
- community applications
- disableSecurityAMD
- turboCache
- moverTuning
- dynamixSSDtrim
I had some problems in the past few day and checked many different ways. Now i am at some point where i have to talk to you.
So my System was runnig great now for 85days.
Some Weeks ago it started to randomly crash and become unresponsive. No WebGUI, no CLI, no reaction when using the keyboard and no reaction when pressing the Boot/Start button on the Chassis.
So i did my research and figured out AMD processors have to be set in BIOS to "typical current idle", changed it and it ran for some days.
Since these changes, the server randomly reboots.
So i changed the CPU freqency tuning settings from "Auto" to a normal fixed Value. Then ist did work for some days and now it randomly reboots again.
Since i had no other Idea and it is getting a little bit anoying.
I hope someone can help me out at this point.
Please see my Diagnostics attached.
In the Syslogfile you will notice there is some Hardware Error with the CPU but i am not quite sure what the this means in detail.
Greetings and stay healthy.
-
So i found this Solution:
Now testing this, maybe this was the issue.
-
On 11/14/2020 at 12:54 AM, klingherit said:
Thanks for your reply! I have attached the syslog.
Hey klingherit,
i am faceing the same Problem so did you find any solution?
-
Just looked into it seems crazy what is needed to run a farming simulator server.This is too complicated. Tried it with Farming Simulator 16, first of all there is no Linux server, only Windows, second you need to install the game by hand (also very complicated because if it works you need to open up a virtual webvnc viewer and enter there the key) and lastly you need an extra license for the Server itself.-
1
-
-
What about a Farming Simulator Server? Like to see this one and should not be to complicated.
-
Hello Unraid Members,
As Squids Common issues plugin showed. I have the CPU Scaling features not implemented and I'm curious, because some days before, i did an BIOS upgrade which set my BIOS settings back. Before my system was working at 25-35W per Hour now I am at 70-110W. I had made some other changes so this doesn't have to be the issue but it could help in some ways.
Greetings and stay healthy.
-
Nice job. I will have look on this. Maybe set another name because Hernanditos CA App looks exactly the same way.Created a new template that works properly and is also available in the CA APP... [emoji6]
@dathomas85 & @D'n'S137 (this is the official container) & @tjb_altf4
Stay healthy.-
1
-
-
Hey,
Go to docker page.
Make sure there is the docker hub page in the Repository list:
Click on add Container give the Container a Name.
As repository set "google/cloud-sdk"(without "" and it is case sensitive)
Set the variables, path and everything else as described in docker hub and hit apply.
https://hub.docker.com/r/google/cloud-sdk/
Greetings, stay healthy
-
Why not use PhotoPrisms docker?
Compose
https://hub.docker.com/r/photoprism/photoprism/
Manual from Documentation
https://docs.photoprism.org/getting-started/docker/
Greetings stay healthy. -
Exactly. Just remove one of the Cables, if possible, and try again. Or stop all containers go into the docker settings and remove one of them by deselect them.Ok ... i've found them and my br2/br3 look like this
- IPv4 custom network on interface br2: Subnet: 192.168.2.0/24 Gateway: DHCP pool: not set
- IPv4 custom network on interface br3: Subnet: 192.168.2.0/24 Gateway: DHCP pool: not set
- Subnet: 192.168.1.0/24 Gateway: 192.168.1.1 DHCP pool: not set
- Could this be the cause and nothing to do with the existing dockers?
-
Thank you for posting your answer.I found a solution around the same time you wrote it.I'm not using let's encrypt like he does. I'm using NGINX Proxy Manager which has let's encrypt built into it.
And while I was doing another thing, I noticed it had a text saying "enable websocket". And I just had to enable it right there.
Thank you anyway though [emoji4]
It's always a good step, to look into the logs most services know what they need [emoji16][emoji106]
-
Do they only use 172.17.0.2? Or is it set like:They are using 172.17.0.2 & 3 respectively. No command line input at all. In bridge mode.
Sent from my CLT-L09 using Tapatalk
172.17.0.2:80 192.168.1.2:80
You can have a look in the Docker Tab.
But as I mentioned before please have a look at the advanced docker settings if there are more than one network set within the same Subnet, there is your Problem. -
Sounds good, and what networks did you configure? Did you run at some point 'docker network create'? As I mentioned before this will setup a network using the 172 as the first octet for the Network Subnet.I only have Maria and nextcloud dockers installed as preconfigured.
Sent from my CLT-L09 using Tapatalk -
Just look into YouTube Spaceinvader One did a great video of the hole StoryHello unRAID people.
I've got the docker installed, tested it works like a charm.
But I'm having an issue I can't figure out how to solve.
I've installed the Rocket Chat app on my Android phone, but I can't connect to the workspace for it before I've enabled the Websocket.
I'm not quite sure what it is, I've read about it needs NGINX, I have the NGINX Proxy Manager, but I can't seem to find what I need.
Can anyone help?
Gesendet von meinem Pixel 3a XL mit Tapatalk
-
Sorry for the late answer you can check your log just after starting the docker from the Unraid Docker Tab at the right by pressing the symbol that looks like a written pice of paper these logs are live when your docker is running.@D'n'S137
ah ok..
3.. I cant really test it i only remote accessing my sisters Unraid to run the FireFox Docker it will work for websites just doesnt like the rocket chat it startes to load the --- dots but then shows up it crashed..
2.. the log files is
also changed my dns to example.com like it will run for a while and then i noticed its shut down.. as i having issues passing it through Pfsense etcErrorWarningSystemArrayLoginat Object.onceWrapper (events.js:418:26)at Socket.emit (events.js:311:20)at errorOrDestroy (internal/streams/destroy.js:108:12)at onwriteError (_stream_writable.js:456:5)at onwrite (_stream_writable.js:483:5) {name: 'MongoNetworkError',[symbol(mongoErrorContextSymbol)]: {}}LocalStore: store created atLocalStore: store created atLocalStore: store created atSetting default file store to GridFS{"line":"120","file":"migrations.js","message":"Migrations: Not migrating, already at version 191","time":{"$date":1593868255927},"level":"info"}Loaded the Apps Framework and loaded a total of 0 Apps!Using GridFS for custom sounds storageUsing GridFS for custom emoji storageBrowserslist: caniuse-lite is outdated. Please run next command `npm update`Updating process.env.MAIL_URL➔ System ➔ startup➔ +--------------------------------------------------------------+➔ | SERVER RUNNING |➔ +--------------------------------------------------------------+➔ | |➔ | Rocket.Chat Version: 3.3.3 |➔ | NodeJS Version: 12.16.1 - x64 |➔ | MongoDB Version: 4.2.8 |➔ | MongoDB Engine: unknown |➔ | Platform: linux |➔ | Process Port: 3000 |➔ | Site URL: https://rocketchat.example.com |➔ | ReplicaSet OpLog: Enabled |➔ | Commit Hash: f9553e4d8f |➔ | Commit Branch: HEAD |➔ | |➔ +--------------------------------------------------------------+/app/bundle/programs/server/node_modules/fibers/future.js:313throw(ex);^MongoNetworkError: failed to connect to server [192.168.0.3:27017] on first connect [Error: write EPIPEat afterWriteDispatched (internal/stream_base_commons.js:154:25)at writeGeneric (internal/stream_base_commons.js:145:3)at Socket._writeGeneric (net.js:780:11)at Socket._write (net.js:792:at doWrite (_stream_writable.js:441:12)at writeOrBuffer (_stream_writable.js:425:5)at Socket.Writable.write (_stream_writable.js:316:11)at Connection.write (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:271:21)at runCommand (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:384:at performInitialHandshake (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:122:3)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:35:5at callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:264:5)at Socket.connectHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:309:5)at Object.onceWrapper (events.js:417:28)at Socket.emit (events.js:311:20)at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1123:10) {name: 'MongoNetworkError',[symbol(mongoErrorContextSymbol)]: {}}]at Pool. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/topologies/server.js:438:11)at Pool.emit (events.js:311:20)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:561:14at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:994:11at callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:97:5)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:124:7at _callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:349:5)at Connection.errorHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:365:5)at Object.onceWrapper (events.js:418:26)at Connection.emit (events.js:311:20)at Socket. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:340:10)at Object.onceWrapper (events.js:418:26)at Socket.emit (events.js:311:20)at errorOrDestroy (internal/streams/destroy.js:108:12)at onwriteError (_stream_writable.js:456:5)at onwrite (_stream_writable.js:483:5) {name: 'MongoNetworkError',[symbol(mongoErrorContextSymbol)]: {}}LocalStore: store created atLocalStore: store created atLocalStore: store created atSetting default file store to GridFS{"line":"120","file":"migrations.js","message":"Migrations: Not migrating, already at version 191","time":{"$date":1594125007398},"level":"info"}Loaded the Apps Framework and loaded a total of 0 Apps!Using GridFS for custom sounds storageUsing GridFS for custom emoji storageBrowserslist: caniuse-lite is outdated. Please run next command `npm update`Updating process.env.MAIL_URL➔ System ➔ startup➔ +--------------------------------------------------------------+➔ | SERVER RUNNING |➔ +--------------------------------------------------------------+➔ | |➔ | Rocket.Chat Version: 3.3.3 |➔ | NodeJS Version: 12.16.1 - x64 |➔ | MongoDB Version: 4.2.8 |➔ | MongoDB Engine: unknown |➔ | Platform: linux |➔ | Process Port: 3000 |➔ | Site URL: https://rocketchat.example.com |➔ | ReplicaSet OpLog: Enabled |➔ | Commit Hash: f9553e4d8f |➔ | Commit Branch: HEAD |➔ | |➔ +--------------------------------------------------------------+=== UnHandledPromiseRejection ===MongoError: interrupted at shutdownat Connection. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:450:61)at Connection.emit (events.js:311:20)at Connection.EventEmitter.emit (domain.js:482:12)at processMessage (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:384:10)at Socket. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:553:15)at Socket.emit (events.js:311:20)at Socket.EventEmitter.emit (domain.js:482:12)at addChunk (_stream_readable.js:294:12)at readableAddChunk (_stream_readable.js:275:11)at Socket.Readable.push (_stream_readable.js:209:10)at TCP.onStreamRead (internal/stream_base_commons.js:186:23)=> awaited here:at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)at app/models/server/raw/NotificationQueue.ts:47:15at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40=> awaited here:at Function.Promise.await (/app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:56:12)at app/notification-queue/server/NotificationQueue.ts:41:21at /app/bundle/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/fiber_pool.js:43:40 {operationTime: Timestamp { _bsontype: 'Timestamp', low_: 1, high_: 1594126069 },ok: 0,errmsg: 'interrupted at shutdown',code: 11600,codeName: 'InterruptedAtShutdown','$clusterTime': {clusterTime: Timestamp { _bsontype: 'Timestamp', low_: 1, high_: 1594126069 },signature: { hash: [binary], keyId: [Long] }},name: 'MongoError',[symbol(mongoErrorContextSymbol)]: {}}---------------------------------Errors like this can cause oplog processing errors.Setting EXIT_UNHANDLEDPROMISEREJECTION will cause the process to exit allowing your service to automatically restart the processFuture node.js versions will automatically exit the process=================================Exception in setInterval callback: MongoError: interrupted at shutdownat Connection. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:450:61)at Connection.emit (events.js:311:20)at Connection.EventEmitter.emit (domain.js:482:12)at processMessage (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:384:10)at Socket. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:553:15)at Socket.emit (events.js:311:20)at Socket.EventEmitter.emit (domain.js:482:12)at addChunk (_stream_readable.js:294:12)at readableAddChunk (_stream_readable.js:275:11)at Socket.Readable.push (_stream_readable.js:209:10)at TCP.onStreamRead (internal/stream_base_commons.js:186:23) {operationTime: Timestamp { _bsontype: 'Timestamp', low_: 1, high_: 1594148401 },ok: 0,errmsg: 'interrupted at shutdown',code: 11600,codeName: 'InterruptedAtShutdown','$clusterTime': {clusterTime: Timestamp { _bsontype: 'Timestamp', low_: 1, high_: 1594148401 },signature: { hash: [binary], keyId: [Long] }},name: 'MongoError',[symbol(mongoErrorContextSymbol)]: {}}/app/bundle/programs/server/node_modules/fibers/future.js:313throw(ex);^MongoNetworkError: failed to connect to server [192.168.0.3:27017] on first connect [Error: write EPIPEat afterWriteDispatched (internal/stream_base_commons.js:154:25)at writeGeneric (internal/stream_base_commons.js:145:3)at Socket._writeGeneric (net.js:780:11)at Socket._write (net.js:792:at doWrite (_stream_writable.js:441:12)at writeOrBuffer (_stream_writable.js:425:5)at Socket.Writable.write (_stream_writable.js:316:11)at Connection.write (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:271:21)at runCommand (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:384:at performInitialHandshake (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:122:3)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:35:5at callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:264:5)at Socket.connectHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:309:5)at Object.onceWrapper (events.js:417:28)at Socket.emit (events.js:311:20)at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1123:10) {name: 'MongoNetworkError',[symbol(mongoErrorContextSymbol)]: {}}]at Pool. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/topologies/server.js:438:11)at Pool.emit (events.js:311:20)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:561:14at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:994:11at callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:97:5)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:124:7at _callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:349:5)at Connection.errorHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:365:5)at Object.onceWrapper (events.js:418:26)at Connection.emit (events.js:311:20)at Socket. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:340:10)at Object.onceWrapper (events.js:418:26)at Socket.emit (events.js:311:20)at errorOrDestroy (internal/streams/destroy.js:108:12)at onwriteError (_stream_writable.js:456:5)at onwrite (_stream_writable.js:483:5) {name: 'MongoNetworkError',[symbol(mongoErrorContextSymbol)]: {}}LocalStore: store created atLocalStore: store created atLocalStore: store created atSetting default file store to GridFS{"line":"120","file":"migrations.js","message":"Migrations: Not migrating, already at version 191","time":{"$date":1594162911636},"level":"info"}Loaded the Apps Framework and loaded a total of 0 Apps!Using GridFS for custom sounds storageUsing GridFS for custom emoji storageBrowserslist: caniuse-lite is outdated. Please run next command `npm update`Updating process.env.MAIL_URL➔ System ➔ startup➔ +--------------------------------------------------------------+➔ | SERVER RUNNING |➔ +--------------------------------------------------------------+➔ | |➔ | Rocket.Chat Version: 3.3.3 |➔ | NodeJS Version: 12.16.1 - x64 |➔ | MongoDB Version: 4.2.8 |➔ | MongoDB Engine: unknown |➔ | Platform: linux |➔ | Process Port: 3000 |➔ | Site URL: https://rocketchat.example.com |➔ | ReplicaSet OpLog: Enabled |➔ | Commit Hash: f9553e4d8f |➔ | Commit Branch: HEAD |➔ | |➔ +--------------------------------------------------------------+/app/bundle/programs/server/node_modules/fibers/future.js:313throw(ex);^MongoNetworkError: failed to connect to server [192.168.0.3:27017] on first connect [Error: write EPIPEat afterWriteDispatched (internal/stream_base_commons.js:154:25)at writeGeneric (internal/stream_base_commons.js:145:3)at Socket._writeGeneric (net.js:780:11)at Socket._write (net.js:792:at doWrite (_stream_writable.js:441:12)at writeOrBuffer (_stream_writable.js:425:5)at Socket.Writable.write (_stream_writable.js:316:11)at Connection.write (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:271:21)at runCommand (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:384:at performInitialHandshake (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:122:3)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:35:5at callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:264:5)at Socket.connectHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:309:5)at Object.onceWrapper (events.js:417:28)at Socket.emit (events.js:311:20)at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1123:10) {name: 'MongoNetworkError',[symbol(mongoErrorContextSymbol)]: {}}]at Pool. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/topologies/server.js:438:11)at Pool.emit (events.js:311:20)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:561:14at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:994:11at callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:97:5)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:124:7at _callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:349:5)at Connection.errorHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:365:5)at Object.onceWrapper (events.js:418:26)at Connection.emit (events.js:311:20)at Socket. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:340:10)at Object.onceWrapper (events.js:418:26)at Socket.emit (events.js:311:20)at errorOrDestroy (internal/streams/destroy.js:108:12)at onwriteError (_stream_writable.js:456:5)at onwrite (_stream_writable.js:483:5) {name: 'MongoNetworkError',[symbol(mongoErrorContextSymbol)]: {}}LocalStore: store created atLocalStore: store created atLocalStore: store created atSetting default file store to GridFS{"line":"120","file":"migrations.js","message":"Migrations: Not migrating, already at version 191","time":{"$date":1594264917618},"level":"info"}Loaded the Apps Framework and loaded a total of 0 Apps!Using GridFS for custom sounds storageUsing GridFS for custom emoji storageBrowserslist: caniuse-lite is outdated. Please run next command `npm update`Updating process.env.MAIL_URL➔ System ➔ startup➔ +--------------------------------------------------------------+➔ | SERVER RUNNING |➔ +--------------------------------------------------------------+➔ | |➔ | Rocket.Chat Version: 3.3.3 |➔ | NodeJS Version: 12.16.1 - x64 |➔ | MongoDB Version: 4.2.8 |➔ | MongoDB Engine: unknown |➔ | Platform: linux |➔ | Process Port: 3000 |➔ | Site URL: https://rocketchat.example.com |➔ | ReplicaSet OpLog: Enabled |➔ | Commit Hash: f9553e4d8f |➔ | Commit Branch: HEAD |➔ | |➔ +--------------------------------------------------------------+/app/bundle/programs/server/node_modules/fibers/future.js:313throw(ex);^MongoNetworkError: failed to connect to server [192.168.0.3:27017] on first connect [Error: write EPIPEat afterWriteDispatched (internal/stream_base_commons.js:154:25)at writeGeneric (internal/stream_base_commons.js:145:3)at Socket._writeGeneric (net.js:780:11)at Socket._write (net.js:792:at doWrite (_stream_writable.js:441:12)at writeOrBuffer (_stream_writable.js:425:5)at Socket.Writable.write (_stream_writable.js:316:11)at Connection.write (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:271:21)at runCommand (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:384:at performInitialHandshake (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:122:3)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:35:5at callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:264:5)at Socket.connectHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:309:5)at Object.onceWrapper (events.js:417:28)at Socket.emit (events.js:311:20)at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1123:10) {name: 'MongoNetworkError',[symbol(mongoErrorContextSymbol)]: {}}]at Pool. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/topologies/server.js:438:11)at Pool.emit (events.js:311:20)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:561:14at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:994:11at callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:97:5)at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:124:7at _callback (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:349:5)at Connection.errorHandler (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connect.js:365:5)at Object.onceWrapper (events.js:418:26)at Connection.emit (events.js:311:20)at Socket. (/app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/connection.js:340:10)at Object.onceWrapper (events.js:418:26)at Socket.emit (events.js:311:20)at errorOrDestroy (internal/streams/destroy.js:108:12)at onwriteError (_stream_writable.js:456:5)at onwrite (_stream_writable.js:483:5) {name: 'MongoNetworkError',[symbol(mongoErrorContextSymbol)]: {}}
By looking into the logs it seems like RocketChat cannot find your mongoDB, you have to have a installed mongoDB docker/server running if you want to run a RocketChat docker/server, if you already have one installed check the Network connection both docker/servers have to be on the same Subnet.
Gesendet von meinem Pixel 3a XL mit Tapatalk
-
Check at Settings -> Docker -> upper right switch to advanced viewIn syslog ...
'rc.docker: Error response from daemon: Pool overlaps with other one on this address space'
Seen it a few times recently.
What Networks are set?
Seems like one is overlapping maybe a Subnet typo or using a Subnet like the standard 172 Network.
Gesendet von meinem Pixel 3a XL mit Tapatalk
-
couple issues with the program.. how do you get rocket chat to start up after mongodb on a boot up.. since Rocketchat doesnt ever wanna load up
unless manual
2nd. issue why is rocket chat working for a while running idle then shuts itself off whats going on...
3rd.. why in Firefox doesnt rocketchat work i trying to use it over the internet and in firefox it trys to load.. and then firefox docker gives the error gah the tabs have crashed.. each time it trys to connect to rocketchat
1 I do it manual
2 check the container logs, any crash information? Any warnings?
3 I would suggest a problem with your Firefox container maybe try it from a real PC with the newest Firefox version.
Gesendet von meinem Pixel 3a XL mit Tapatalk
-
Hello Guys, Rocket.Chat up and running everything is fine.
Are you planning to Update the Docker Container to the newest Version? If so when are you planning to release these Update?
-
21 hours ago, Frank1940 said:
google unraid.net amd ryzen problems
And read the posts from Unraid.net first. You can read the ones on Reddit if you want more information.
Okay so Thanks for your advise.
I disabled C-States and SMT features, since i had no Problems at all.
But i was wondering why can i run the Server for some days bevor and now i get these errors, because C-States were active all the time. -
Thanks for your experience report. It leads me to search for my Problem at AMD, some other people had similar issues with the same CPU it seems to be a Problem with the C-States and the SMT feature so I disabled C-States in my BIOS. Now I am testing if this solved my Problem. But I will reach out for the AMD support because it seems like they know the issue, with these Ryzen 7 1700(x) CPUs.I ran into MCEs with my old server. The recommendations from here were that I contact the CPU & motherboard vendors to see if there was anything they could do/help with. I ended up having to replace the CPU.
Not saying that's guaranteed to be your only course of action here, but bracing you for the worst. Wait for someone more knowledgeable to chime in, but you may want to at least start checking with your vendors.
Gesendet von meinem Pixel 3a XL mit Tapatalk
-
At last boot i got no errors after two hours the system crashed again i had to reset the system(hard shutdown). Today i booted the system an got some errors in the LOG see below:
May 24 17:36:58 MPS kernel: Warning: PCIe ACS overrides enabled; This may allow non-IOMMU protected peer-to-peer DMA May 24 17:36:58 MPS kernel: tsc: Fast TSC calibration failed May 24 17:36:58 MPS kernel: ACPI: Early table checksum verification disabled May 24 17:36:58 MPS kernel: mce: [Hardware Error]: Machine check events logged May 24 17:36:58 MPS kernel: mce: [Hardware Error]: CPU 4: Machine Check: 0 Bank 5: bea0000000000108 May 24 17:36:58 MPS kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff8168b28a MISC d012000100000000 SYND 4d000000 IPID 500b000000000 May 24 17:36:58 MPS kernel: mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1590334600 SOCKET 0 APIC 8 microcode 8001138 May 24 17:36:58 MPS kernel: mce: [Hardware Error]: Machine check events logged May 24 17:36:58 MPS kernel: mce: [Hardware Error]: CPU 8: Machine Check: 0 Bank 5: bea0000000000108 May 24 17:36:58 MPS kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffff8168b28a MISC d012000100000000 SYND 4d000000 IPID 500b000000000 May 24 17:36:58 MPS kernel: mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1590334600 SOCKET 0 APIC 1 microcode 8001138 May 24 17:36:58 MPS kernel: floppy0: no floppy controllers found May 24 17:36:58 MPS kernel: ccp 0000:07:00.2: psp initialization failed May 24 17:36:58 MPS kernel: ACPI Warning: SystemIO range 0x0000000000000B00-0x0000000000000B08 conflicts with OpRegion 0x0000000000000B00-0x0000000000000B0F (\GSA1.SMBI) (20180810/utaddress-204) May 24 17:36:58 MPS kernel: ata5.00: failed to enable Sense Data Reporting, Emask 0x1 May 24 17:36:58 MPS kernel: ata5.00: failed to enable Sense Data Reporting, Emask 0x1 May 24 17:36:58 MPS kernel: ata6.00: failed to enable Sense Data Reporting, Emask 0x1 May 24 17:36:58 MPS kernel: ata6.00: failed to enable Sense Data Reporting, Emask 0x1 May 24 17:37:11 MPS rpc.statd[1972]: Failed to read /var/lib/nfs/state: Success
Do i have a bad CPU? Are there any reliable hardware test? I bought the CPU *used* to save a bug, maybe this was a scam/mistake.
-
Hello all,
My Situation: fresh System installed since 3 Month with new UNRAID V6, works fine for weeks, used Docker(lancache, folding@home, jdownloader[query downloads with slow internet]) also used VMs Windows and Linux and i had have some SMB and APF shares.
Problem: My system crashes randomly after some time, even with no docker and no VMs started. When the system crashes it needs to be shutdown manually, i can´t login to the webUI and also the console is not responding but i still get my hourly Array Status and can ping the systems IP-Address.
I have inserted an USB-Networkcard, i will make a test without it.- No change! -
In the logs Folder there are no logs.Greetings
-
1 hour ago, jonathanm said:
Not sure what you are saying here. Parity as implemented in Unraid only recreates a missing or failed disk, it doesn't back up anything. Important data must exist in multiple physical locations and not be effected by issues with a single system. True backups are some form of
Parity is much less important than real backups, and most of the time money spent on a second parity drive would be much better allocated to a real backup.
"more parity" = "more parity drives"
Random Shutdown MCE Unraid 6.8.3
in General Support
Posted
I Backedup my data from the System(in SafeMode with GUI) to another Drive, to do so i had to take one of the CacheDrives out of my System, because otherwise i ran into an licence issue.
I noticed since the hole copying process my system runs fine. So i gave it a try put the CacheDrive back in and rebooted the system. After like 1 and a half hour the system crashed again. I removed the CacheDrive again and rebooted into SafeMode with GUI started the array an let the system run. After 17 Hours the system crashed again right next to me.
So it beeps twice and then reboots without warning or any singn of shutdown script. The screen goes black, it beeps twice and reboots.
maybe a hardware error or an stability issue from the Mainboard config.
I will do some further Testing:
Open Questions to me:
Maybe someone can help me with one of those questions.
Kindly Greetings