comet424

here is my network settings if the diagnostics dont show anything

i found the cfgs on the flash drive.. can i just delete the folder? and will unraid re add to flash drive .. update.. i ended up shutting down unraid pulled the usb and renamed teh shares folder.. now i re installed it booted up.. ya got some errors for the cache settings etc fixing thos i still cant do \\tower only 1 share shows up i cant even get tower/ (in the browser to work) which is weird but 192.168.0.3/ works but ya cant get damn shares to work doing \\tower but i can do the other server names like mitchflix/ backupserver/ in the browser just not tower/ here's a new diagnostic file if you see anything else tower-diagnostics-20200711-2125.zip

can i not delete those cfg files and let unraid fix itself again? like refresh the shares? oh and i re tried \\192.168.0.3 it was quick... . \\tower was slow and still only displays the 1 share

i deleted the one vm in the lib file now i had to redownload the diagnostic file without the anyomous option.. i looked at the shares.. but there are a bunch that dont exisit.. i tried Bin-Krusader and checked each Disk... those first few shares dont exist in there where else would these shares be? so thats messed it up.. its finding shares that dont actually exisit anymore they were deleted long ago or should have been

so i disabled cache drive and spun up disks \\192.168.0.3 was almost instant \\tower was pretty instant but you see in the pics its not displaying properly tower and 192.168.0.3 are the same server

what does the log file say the errors are ? i think that is one of the vms that doesnt work anymore i had issues with my webserver so i have done a few reinstall vms.. maybe that is one of them.. i counted the shares.. it shows only 39 and a few of them i have are just temporay i copied files off bad array disk so i be dropping some.. how do you see those shares.. when i goto "Shares" i only counted 39, and some of those are temporary for now.. ok i can try the spin up.. and yes im using Windows 10 as the client well like i mentioned if i do \\192.168.0.3 (tower) it populates instantly... but if i do \\tower it takes time sometimes doesnt work i have to do it a second time but then all it does it shows one of my Shares from the 39.. but doing \\192.168.0.3 populates them instantly ya i using the cache directories plugin i honestly dont know if its working really as it seems fast for the first or 2nd subfolders but then slow as molasses after.. i not sure how many files its caching i just installed it and left it as the default i was hoping since i have 32gb of ram it would load the whole thing into ram,, but ill try turning it off.. i know i use a program called Virtual DJ as i dj play music off the array and i find it locks up and even accessing the files is an issue.. so i moved the files in Tower under 1 drive under an ussasigned drive... but still find issues .. and i noticed the system log i got a sdd the unassigned drive error.. but there is no smart errors i checked drive so not sure what that is Jul 11 17:13:50 Tower kernel: print_req_error: I/O error, dev sdd, sector 98099912 what is that error.. and how do i find duplicate shares as "Common Fixes" didnt find no issues but ill try turning off the cache directories and see

i already commented in the other unraid form for the other server for Random Unraid reboots... as other people are experiencing Unraid randomy rebooting on them.., but you were the one asking about the names of the 2 servers that there acting up.. this topic is just for the 1 server.. and the other server i mentioned about hopefully someone has answers in the other form...... as for puncuation etc.. good luck i have dislexia, and other disorders, id have someone proof read before sending it. But ill try my best. as for server names.. they fine.. Backupserver,mikeflix,mitchflix, and tower... and the issue of the Tower only happened in last couple days.. its been running not bad for the past 2 yrs.. the Tower,Backupserver,Mitchflix, and Mikeflix Unraids all have static IPs. Tower (192.168.0.3) when doing "\\tower" it only shows 1 of the Share Roots. and only shows 1 file folder inside that Root share when i do "\\192.168.0.3" For Tower, it shows all my Share roots and my other folders in the 1 its only displaying when i do \\tower and here is diagnostic file.. it took alot longer to make it for some reason.. and if you see any other errors in there let me know so i can fix them too.. that i havent noticed Hopefully that Helps you.. also there are no common errors either from running Common fix tower-diagnostics-20200711-1715.zip

Tower and mitchflix i have other unraid servers but they seem to be working not issues Tower 192.168.0.3 (\\tower shows up 1 Share Folder) (\\192.168.0.3 shows all the folders no issues) mitchflix 192.168.0.8 (this one is having issues of unraid rebooting on its own and it doesnt have parity just randomly reboots at times and no errors just started in teh past week i noticed ) both unraid servers i also noticed randomy Dockers shut themselves off too

last few days unraid been acting weird on 2 of my servers different things on each one but this one really messed if i type \\tower i only get 1 File folder to show up in windows and it takes time for it to load too (green bar goes across the screen in file explorer slowly) if i type \\192.168.0.3 i see all my folders instantly (roughly 20 folders) have you guys run into an issue like this or know how to fix it or where else to look

same here my one unraid it randomly reboots on its own.. as i loose access to the docker.. i also find dockers turn themselves off on there own on 2 of my unraids but no system logs and i looked at the start here but that didnt explain anything.. since there is no parity drive on the unraid thats rebooting it started in the past week that i noticed

anyone know how to stop krusader from crashing when you do a file search i tried and uninstall and reinstall of the docker.. yet still crashes after like 10 or 20min into the search of the array

why does krusader constantly crash if i use the File Search under /media location.. it works for a while then crashes (stops) and i have to restart it only to find out it crashes again

@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 etc ErrorWarningSystemArrayLogin 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 at LocalStore: store created at LocalStore: store created at Setting 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 storage Using GridFS for custom emoji storage Browserslist: 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:313 throw(ex); ^ MongoNetworkError: failed to connect to server [192.168.0.3:27017] on first connect [Error: write EPIPE at 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:8) 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:8) 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:5 at 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.<anonymous> (/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:14 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:994:11 at 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:7 at _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.<anonymous> (/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 at LocalStore: store created at LocalStore: store created at Setting 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 storage Using GridFS for custom emoji storage Browserslist: 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 shutdown at Connection.<anonymous> (/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.<anonymous> (/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:15 at /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:21 at /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 process Future node.js versions will automatically exit the process ================================= Exception in setInterval callback: MongoError: interrupted at shutdown at Connection.<anonymous> (/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.<anonymous> (/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:313 throw(ex); ^ MongoNetworkError: failed to connect to server [192.168.0.3:27017] on first connect [Error: write EPIPE at 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:8) 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:8) 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:5 at 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.<anonymous> (/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:14 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:994:11 at 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:7 at _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.<anonymous> (/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 at LocalStore: store created at LocalStore: store created at Setting 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 storage Using GridFS for custom emoji storage Browserslist: 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:313 throw(ex); ^ MongoNetworkError: failed to connect to server [192.168.0.3:27017] on first connect [Error: write EPIPE at 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:8) 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:8) 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:5 at 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.<anonymous> (/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:14 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:994:11 at 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:7 at _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.<anonymous> (/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 at LocalStore: store created at LocalStore: store created at Setting 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 storage Using GridFS for custom emoji storage Browserslist: 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:313 throw(ex); ^ MongoNetworkError: failed to connect to server [192.168.0.3:27017] on first connect [Error: write EPIPE at 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:8) 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:8) 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:5 at 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.<anonymous> (/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:14 at /app/bundle/programs/server/npm/node_modules/meteor/npm-mongo/node_modules/mongodb/lib/core/connection/pool.js:994:11 at 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:7 at _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.<anonymous> (/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)]: {} }

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

@TexasUnraid ok thank you.. least its something... ya it was driving me nuts and would been ok if pressing Del would send it to the .Recylin.Bin not the Trash99 folder.. as if you do a MOVE in krusader to Recylin.Bin goes instant.. but when you use the DEL it takes forever frustrating at times.. but ill give that a try

hi maybe you guys can point me in right direction.. i setup the mongo and rocketchat and got it to work.. but i cant get it to work over WAN i use PFsense as my router i looked under dns forwarder but it doesnt like you do rocketchat.myhouse.mine.nu and forward it to 192.168.0.2:3000 how do i get it work over the wan when you have pfsense

hi with the pandemic i decided to move my music from my External Hard drives to the array and re use the hard drives for something else.. so i DJ weddings etc and carry music on external hard drives with me using NTFS format but i been having issues i made a share and map network drive like X: to my music folder and my array is using BTRFS also it saves a database and virtual folders on the X: drive map location of my favorites you can say of songs.. also i set when i made the share that DISKx would be specificially to music so i wouldnt need to spin up the entire array just the one disk and i guess the PArity drive too but i find its locking up the software.. and i also noticed the drive was also spinning down when i was supposedly accessing the music... the database it uses is a XML file located on the drive it scans for certain songs... my question if anyone has done this or similar or something how to avoid it from locking up my dj software it goes in an endless loop my idea was i could keep the music on the array and its protected by the Parity drive.. but just seems software is not liking it.. and i perfer the drive to spin down when not in uuse as its just one of my data disks.. currently i trying i shoved a HD into my unraid as an unnasigned NTFS drive and mapped my music to it.. and hopefully no issues then.. but i was wanting it protected when i added new music... is it because my Filesystem is BTRFS and NTFS for my dj music... is it because the database is on Data Disk with Parity that is constantly checking and Writting when i modify in program and it alters the Database.. i know not unraid question i just was hoping maybe someone in my similar situation was able to point me what they have done to fix it etc

@cbr600ds2 ah that is weird.. least its working. I was going to say maybe your router isn't doing like Upnp or ports for the unraid but its open on your normal computer least you were able to solve it..

@cbr600ds2 this is the settings I do so /downloads is the root /downloads/incomplete is the files being downloaded /downloads/complete is the files completed...

host path 2 container path is /downloads Host path is /mnt/disks/SATA_SSD.... Slave Read Write and host path 3 container path is /watch Host path is /mnt/disks/SATA_SSD/watch Slave Read Write and make sure to move all the torrents off your cache drive to your 1TB before restarting transmission as you make have to do the verify data in transmission it should work for you.. if your using a VPN like NordVPN they are experiencing issues and many of there servers are down so your transmission trackers wont be working

@pika I been waiting since January since I had same issue with the X570 boards but looks promising in the next release fingers crossed

wait till the next release of unraid. or supposed to be fixed in Beta version.. and there is a driver for unraid they working on GitHub.. to try to fix the issue

hi i had to replace my Sata Cache 1tb as it was having CRC errors and i experienced slowness of the Docker when you click it.. and slowness of the VMS.. so i decided to go with a NVME 3500/3000 SSD i get those speeds in Windows close to it.. and in unraid the diskspeed test says i get 2500 roughly.. so i dunno why its slow there. but i finding 1.. i have had to reinstall docker 3 times in the past 2 weeks it keeps poping up saying my docker could corrupt from an older beta.. so delete and re install.. im currently doing it again right now.. since i trying to fix the speed.. 2.. i have set the notifications never to check for updates.. and i have the ca update to do it once a day. so when i load up docker it be slow takes like 10 seconds. or so... but after that.. i go to any other tab.. and go back to docker its instantly there... its like if it was spinning up drives to access.. but no all the appdata, docker,system,iso are all saved on the SSD cahce... i dont use the cache drive for file transfers. as i dont waant to save the life of the SSD as the Sata was less then 6 months old i RMA and was 88% life left.. so i only using for those 4 directories is there anything else i can check why dockers so slow... i also made sure no more errors anymore with Fix Commons... those test with no errors.. and it be the rest of the day to reinstall the 26 Docker items to reinstall.. but i only have 1-3 usually running at one time anyways.. but is there anything else i can check why its slow.. shouldnt it be lighting fast with the nvme?

guess I fixed it lol.. had to install bonic then uninstall it.. and that removed it... as this computer is 16 yr old computer single core and only for backup... didn't want to install it but I did but uninstalled after.. plus only 2gb or ram lol

one way to get you to install either one by not allowing to be deleted.. but it doesn't go away.. even after you install the app lol guess ill format and hope for the best.. by design frig sakes lol