Kazino43

Hi, dislcaimer: noobie here! I wanted to install a new container (notifying me of new rental apartments) which does not exist in CA/Dockerhub. There is only a Github Repo with a Dockerfile: https://github.com/0a1b/ebay-kleinanzeigen_enhanced From what I found out, there is a way to create a container via a dockerfile like in this casein unRaid. 1. clone/download the full repo 2. (in this case) add the Telegram-Bot-Token as well as any kind of character to "DEBUG=" in the .env file. 3. in the unRaid-GUI open the console: 3.1 cmd: "docker build -tag TAG:NAME /mnt/way/to/folder 4. So far it did create the image successfully: " Successfully built 9be18592bca2 // Successfully tagged kleinanzeigen:bot" 5. Add a Container via GUI and select the TAG:NAME as the repo The only problem I have right now is if I did everything right, because it seems like there is something missing. In container-log-window it mentions some errors regarding the telegram-token handeling it seems: Traceback (most recent call last): File "/app/main.py", line 187, in <module> main() File "/app/main.py", line 156, in main updater = Updater(bot=utils.get_bot(), use_context=True) File "/app/utils.py", line 18, in get_bot return Bot(token=os.getenv("TG_TOKEN"), request=request) File "/usr/local/lib/python3.8/site-packages/telegram/bot.py", line 194, in __init__ self.token = self._validate_token(token) File "/usr/local/lib/python3.8/site-packages/telegram/bot.py", line 353, in _validate_token if any(x.isspace() for x in token): TypeError: 'NoneType' object is not iterable Traceback (most recent call last): File "/app/main.py", line 187, in <module> main() File "/app/main.py", line 156, in main updater = Updater(bot=utils.get_bot(), use_context=True) File "/app/utils.py", line 18, in get_bot return Bot(token=os.getenv("TG_TOKEN"), request=request) File "/usr/local/lib/python3.8/site-packages/telegram/bot.py", line 194, in __init__ self.token = self._validate_token(token) File "/usr/local/lib/python3.8/site-packages/telegram/bot.py", line 353, in _validate_token if any(x.isspace() for x in token): TypeError: 'NoneType' object is not iterable I added everything (token as well as a not-empty-value behind "DEBUG=") in the ".env"-file from the repo. But it seems like it either doesn't recognize the .env file (do I need to add some paths in the Template while adding the container?) or it is limitied in connecting to the telegram servers (the container is set to "Network type: Bridge". I would appreciate any help. Sitting here for the last 5 hours trying everything and kind of giving up at this moment. :(

Auf dem Cache war nichts mehr. Warum wird nun aber nicht einmal das Backup ordentlich eingespielt, sondern hängt sich irgendwo auf? Ich gehe wie folgt vor: 1. Ordner: /mnt/user/iobroker_new/data 2. dort wird das Backup abgelegt 3. daraufhin wird die Wiederherstellung gestartert und endet bei: "host.6566d07bb05a check instance "system.adapter.web.0" for host "814b5ca53ca4" Das Backup müsste doch, unvoreingenommen, was davor passiert ist, nehmen, oder mache ich was falsch? Edit: Warscheinlich hat das hier nun was mit dem anderen Hostnamen zu tun, jedoch kann ich den Hostnamen nicht ändern mit "iobroker host oldHostName.", weil er mir sagt, dass ich wieder erst iobroker stoppen sollte: "Cannot execute changes on running system. Stop iobroker first." Jedoch reagiert er auf "iobroker stop" nicht, es kommt nur "iobroker controller daemon is not running". Gibt es für den unRaid Container einen anderen Befehl, "iobroker stop" zu ersetzen?

Danke @mgutt für die Antwort. Das obige Problem konnte ich über den "ioBroker"-internen Adapter "Backit" lösen, indem ich im Container selbst das Backup widerhergestellt habe über "iobroker restore 0". Danach zur Sicherheit wieder den gesamten appdata Ordner mit dem CA-Plugin gesichert. Nun habe ich über den Mover den appdata share auf "prefer cache" gestellt (zuvor lief alles auf dem Array selbst, weil es noch ein Test war). Dabei habe ich jetzt das Problem, dass mal wieder nur ioBroker Probleme macht. Alle anderen Container funktionieren nach dem Mover-Durchlauf einwandfrei. Dabei habe ich jetzt wieder das zuvor noch funktionierende appdata-Backup eingespielt, es kann also nicht daran liegen. Folgende Fehlermeldung im ioBroker-Log: -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- There is data detected in /opt/iobroker but it looks like it is no instance of ioBroker or a valid backup file! Please check/ recreate mounted folder or volume and start over. Nun geht aber auch die Console des Adapters nicht: Um "iobroker restore 0" durchzuführen, muss zuvor "iobroker stop" ausgeführt werden, dies wird auch bestätigt "iobroker daemon stopped". Wenn ich dann jedoch mit "iobroker restore 0" die Wiederherstellung anstupsen möchte, sagt er mir, dass ich iobroker erst stoppen müsste. Komme also nicht weiter. Edit: Nun einen neuen Ordner für den Container gemacht und dort die Backup-Datei hineingefügt, damit wurde da Backup endlich angestoßen, es tut sich jedoch seitdem nichts: -------------------------------------------------------------------------------- ----- Step 2 of 5: Detecting ioBroker installation ----- -------------------------------------------------------------------------------- IoBroker backup file detected in /opt/iobroker. Preparing restore... Done. Restoring ioBroker... Done. !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! !!!!! IMPORTANT NOTE !!!!! !!!!! The sartup script restored iobroker from a backup file. !!!!! !!!!! Check /opt/iobroker/log/restore.log to see if restore was successful. !!!!! !!!!! When ioBroker now starts it will reinstall all Adapters automatically. !!!!! !!!!! This might be take a looooong time! Please be patient! !!!!! !!!!! You can view installation process by taking a look at ioBroker log. !!!!! !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! -------------------------------------------------------------------------------- ----- Step 3 of 5: Checking ioBroker installation ----- -------------------------------------------------------------------------------- (Re)Setting folder permissions (This might take a while! Please be patient!)... Done. Fixing "sudo-bug" by replacing sudo in iobroker with gosu... Done. -------------------------------------------------------------------------------- ----- Step 4 of 5: Applying special settings ----- -------------------------------------------------------------------------------- Some adapters have special requirements/ settings which can be activated by the use of environment variables. For more information take a look at readme.md on Github! There is no data detected in /opt/userscripts. Restoring exapmple userscripts... Done. -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... ================================== > LOG REDIRECT system.adapter.admin.0 => true [starting] host.6566d07bb05a check instance "system.adapter.admin.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.influxdb.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.javascript.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.mqtt.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.sonoff.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.backitup.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.discovery.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.easee.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.info.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.jarvis.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.mystrom.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.sourceanalytix.0" for host "8911b51aead4" host.6566d07bb05a check instance "system.adapter.web.0" for host "8911b51aead4" weiter gehts nicht. Bin mittlerweile echt am Verzweifeln.

Hallo allseits, ich habe meine kleinen 2TB Platten gegen eine große gewechselt, dazu gemäß wiki vorgegangen: https://wiki.unraid.net/Replacing_Multiple_Data_Drives_with_a_Single_Larger_Drive "faster methode" Nun geht jedoch der ioBroker Container nicht mehr. Alle anderen funktionieren jedoch weiterhin einwandfrei. Der Log des ioBroker Containers von @mguttspuckt aus: -------------------------------------------------------------------------------- ----- Step 5 of 5: ioBroker startup ----- -------------------------------------------------------------------------------- Starting ioBroker... doc.rows is not iterable TypeError: doc.rows is not iterable at Object.getInstancesOrderedByStartPrio (/opt/iobroker/node_modules/iobroker.js-controller/lib/tools.js:2863:27) at async getInstances (/opt/iobroker/node_modules/iobroker.js-controller/main.js:2707:23) object system.meta.uuid cannot be updated: Error: DB closed object system.user.admin created Leider verstehe ich die Fehlermeldung gar nicht und weiß Stand jetzt auch nicht weiter. Habe das Image neuinstalliert, hat uch nichts gebracht. Wisst ihr, woran das liegen könnte und wie man das Problem beheben könnte?

It doesn't work at all. Getting it to sleep manually and with Dynamix Sleep automatically on schedule works great. But waking up doesn't work really. It wakes up, when I send a WOL signal from another PC or router, but not with this script. -Time is set correctly in the settings. -The script above: is modified for testing to wake up 2-3min. after manual sleep, so I mean those time stamps (3 all in all ) are set with a different time stamps, 2 or 3 mins in the future. Just for the safety of using it wrong: It should be put in the "Custom commands before sleep:"? Tried both, but it didn't work either way. EDIT: AWW... Seems like it needs to shut down by itself (not manually) in order to run the script. I'm stupid, but tbh didn't thought this condition needs to be like that. I thought, that for the system, it is the same. But still one question: In which cistom comand box should it go: "Custom commands before sleep:" or "Custom commands after wake-up:" or both?

Although last post is a bit older, I'm also interested in a fixed script for waking up every day at the same time. My notebook (running unRAID on) isn't supporting it by default in the bios. Would be really nice, if someone could help me.