Lebowski Posted January 8, 2021 Share Posted January 8, 2021 19 minutes ago, spants said: can you do an ls -al on that directory please? Thanks, Quote Link to comment
Lebowski Posted January 8, 2021 Share Posted January 8, 2021 Anything I need to change? Quote Link to comment
UNOPARATOR Posted January 9, 2021 Share Posted January 9, 2021 On 1/3/2021 at 11:20 PM, spants said: You may have to keep changing it as the template is not refreshed on the update. Check your /boot/config directory structure for the cached templates and also edit it there Sent from my SM-N976B using Tapatalk The latest update (v1.2.7) went fine and I didn't have to do anything by hand. Cheers! Quote Link to comment
Lebowski Posted January 19, 2021 Share Posted January 19, 2021 @spants Just double checking if I need to change anything? Docker is working just fine as the broker, I still have this error Quote Link to comment
spants Posted January 19, 2021 Author Share Posted January 19, 2021 (edited) @Lebowski sorry for the delay in the reply. please try this fix: Change the permissions of the appdata directory for your MQTT data: for example: chown -R nobody:users /mnt/user/appdata/MQTT and you should be ok. Edited January 19, 2021 by spants Quote Link to comment
Lebowski Posted January 19, 2021 Share Posted January 19, 2021 Still have the issue (if it's an issue!) @spants that didnt seem to fix it. Quote Link to comment
spants Posted January 20, 2021 Author Share Posted January 20, 2021 @Lebowski that is strange. That error looks to be caused by having persistence=true in the config file and not being able to write the mosquitto.db file. Can you share the config file (delete any private bits) ? Quote Link to comment
Lebowski Posted January 22, 2021 Share Posted January 22, 2021 (edited) @spants Sure, here is the config: If I need to change it to false that's fine. I wasn't even sure if its an issue as everything is functioning just fine. # Place your local configuration in /config/conf.d/ retry_interval 20 sys_interval 10 store_clean_interval 10 max_inflight_messages 40 max_queued_messages 200 queue_qos0_messages false message_size_limit 0 allow_zero_length_clientid true persistent_client_expiration 3m allow_duplicate_messages false autosave_interval 60 autosave_on_changes false allow_anonymous false persistence true persistence_file mosquitto.db persistence_location /config/data/ user mosquitto # Port to use for the default listener. listener 1883 listener 9001 protocol websockets log_dest stderr log_type all connection_messages true log_timestamp true include_dir /config/conf.d # If the password.mqtt file is empty, this has no effect. allow_anonymous true # DO NOT CHANGE THIS LINE BELOW!!! password_file /config/passwords.mqtt Edited January 22, 2021 by Lebowski Quote Link to comment
Tsumitsuki Posted January 22, 2021 Share Posted January 22, 2021 about two weeks ago i setup this docker for my smarthome stuff. since then it was ideling cause i haven't setup my devices yet. Today i checked unraid and saw the docker stopped. i wanted to set my devices up this weekend but i cant get the docker up again. every time i start the docker i get this: Warning: store_clean_interval is no longer needed. 1611308988: Error: No error information. 1611308988: Error: Couldn't open database. Warning: store_clean_interval is no longer needed. 1611308997: Error: No error information. 1611308997: Error: Couldn't open database. After this error the docker stops itself again. i havent changed anything. no update, no config changes. i tryed to remove the docker completly and set it up from scratch but still the same error. any idea? Quote Link to comment
spants Posted January 22, 2021 Author Share Posted January 22, 2021 7 hours ago, Tsumitsuki said: about two weeks ago i setup this docker for my smarthome stuff. since then it was ideling cause i haven't setup my devices yet. Today i checked unraid and saw the docker stopped. i wanted to set my devices up this weekend but i cant get the docker up again. every time i start the docker i get this: Warning: store_clean_interval is no longer needed. 1611308988: Error: No error information. 1611308988: Error: Couldn't open database. Warning: store_clean_interval is no longer needed. 1611308997: Error: No error information. 1611308997: Error: Couldn't open database. After this error the docker stops itself again. i havent changed anything. no update, no config changes. i tryed to remove the docker completly and set it up from scratch but still the same error. any idea? Does your MQTT directory look like this?: You can also try setting open permissions on that directory: cd /mnt/user/appdata chmod -R 777 MQTT Quote Link to comment
Tsumitsuki Posted January 22, 2021 Share Posted January 22, 2021 8 minutes ago, spants said: Does your MQTT directory look like this? Yes it dose look like this. 9 minutes ago, spants said: You can also try setting open permissions on that directory: cd /mnt/user/appdata chmod -R 777 MQTT Still the same error. Quote Link to comment
spants Posted January 22, 2021 Author Share Posted January 22, 2021 1 minute ago, Tsumitsuki said: Yes it dose look like this. Still the same error. if you dont need persistance, please edit the mosquitto.conf: persistence false persistence_file mosquitto.db persistence_location /config/data/ and restart MQTT... Quote Link to comment
Tsumitsuki Posted January 22, 2021 Share Posted January 22, 2021 7 minutes ago, spants said: if you dont need persistance, please edit the mosquitto.conf: persistence false persistence_file mosquitto.db persistence_location /config/data/ and restart MQTT... Do i need it? I don't know. For what would i need it as persistend? Sorry for the dumb question, but first time using something like mqtt for me. And yes, without the db it starts just fine. Quote Link to comment
spants Posted January 22, 2021 Author Share Posted January 22, 2021 If you use RETAINED topics, it can write them to a temporary db in case of restarting. Most people dont need this. There seems to be a permissions issue with some dockers, I should take a look at this as I made it some time ago (it just works for me!). I saw on another thread that someone had similar issues on another docker and was advised to run a script (attached). It will reset the directory permissions on the appdata directory. Run it at your own risk (I just tried it) fixAppdataPerms.sh 1 Quote Link to comment
Lebowski Posted January 23, 2021 Share Posted January 23, 2021 Neither options worked (including the script) but I can simply disable it as I am not using it. Quote Link to comment
gulo Posted February 7, 2021 Share Posted February 7, 2021 Hello I would like to use Watch Node / File In Node in Node Red to read files, but I am not sure how I can access my Unraid shared folders? I tried "\\192.168.1.10\ShareName" but Node Red doesn't see it / can't access. Do I need to somehow map those share folders in the Node Red docker configuration? Thanks! Quote Link to comment
UNOPARATOR Posted February 9, 2021 Share Posted February 9, 2021 On 2/7/2021 at 10:28 PM, gulo said: Hello I would like to use Watch Node / File In Node in Node Red to read files, but I am not sure how I can access my Unraid shared folders? I tried "\\192.168.1.10\ShareName" but Node Red doesn't see it / can't access. Do I need to somehow map those share folders in the Node Red docker configuration? Thanks! You might try `smb://192.168.1.10/ShareName` or like you mentioned try to add the necessary share in your Node-RED template. Quote Link to comment
Skylord123 Posted February 10, 2021 Share Posted February 10, 2021 On 2/7/2021 at 12:28 PM, gulo said: Hello I would like to use Watch Node / File In Node in Node Red to read files, but I am not sure how I can access my Unraid shared folders? I tried "\\192.168.1.10\ShareName" but Node Red doesn't see it / can't access. Do I need to somehow map those share folders in the Node Red docker configuration? Thanks! When you create or edit docker containers you can mount folders and files on the host to locations inside the container. Example: I mount my /mnt/user/share/media directory to /media_share in the container for storing timelapse photos. 1 Quote Link to comment
gulo Posted February 12, 2021 Share Posted February 12, 2021 On 2/9/2021 at 6:32 PM, Skylord123 said: When you create or edit docker containers you can mount folders and files on the host to locations inside the container. Example: I mount my /mnt/user/share/media directory to /media_share in the container for storing timelapse photos. Oh, this was easier than I thought Thank you Skylord123 and UNOPARATOR! Quote Link to comment
mavrrick Posted March 30, 2021 Share Posted March 30, 2021 I have recently run into a snag that i believe has been determined to be related to the version of Node.JS used by Node red in the docker. Is there any way to upgrade that to a newer version? Quote Link to comment
spants Posted March 31, 2021 Author Share Posted March 31, 2021 On 3/30/2021 at 1:29 PM, mavrrick said: I have recently run into a snag that i believe has been determined to be related to the version of Node.JS used by Node red in the docker. Is there any way to upgrade that to a newer version? Which version of NodeJS do you need? You can change the version by using the appropriate tag in the Repository field: https://hub.docker.com/r/nodered/node-red/tags?page=1&ordering=last_updated Quote Link to comment
mavrrick Posted May 1, 2021 Share Posted May 1, 2021 On 3/31/2021 at 12:52 PM, spants said: Which version of NodeJS do you need? You can change the version by using the appropriate tag in the Repository field: https://hub.docker.com/r/nodered/node-red/tags?page=1&ordering=last_updated I ended up just setting up a VM and installing everything manually. It was easy enough. I needed atleast Node.js 12 i think, and maybe Node.JS 14. Thanks for advice. Quote Link to comment
spants Posted May 1, 2021 Author Share Posted May 1, 2021 28 minutes ago, mavrrick said: I ended up just setting up a VM and installing everything manually. It was easy enough. I needed atleast Node.js 12 i think, and maybe Node.JS 14. Thanks for advice. No problem. If you needed Node.js 12 - just use nodered/node-red:latest-12 in the repository field of the template Quote Link to comment
TheBurgundyBear Posted May 12, 2021 Share Posted May 12, 2021 For the life of me, I can't figure out how to get the timezone to be correct in Node-RED! Server time is correct. Has anyone run into this issue and resolved it? Quote Link to comment
TheBurgundyBear Posted May 14, 2021 Share Posted May 14, 2021 On 5/12/2021 at 9:51 AM, TheBurgundyBear said: For the life of me, I can't figure out how to get the timezone to be correct in Node-RED! Server time is correct. Has anyone run into this issue and resolved it? Looks like it was as easy as opening a console in the container and typing "TZ=America/Chicago" 1 Quote Link to comment
Recommended Posts
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.