NewDisplayName

I created the following script (it makes nextcloud scan all files to add files which were not uplodaed thru app (e.g. SMB) Is it possible to display something to the unraid log about this script run?

Thanks CHBMB for this app! Nextcloud makes me loose my last hair... I found the following problem after many grey hairs: [03-May-2018 19:58:47] WARNING: [pool www] server reached pm.max_children setting (5), consider raising it Then i tried to make it higher, but it wont accept the localphp.ini, as it seems. Now i read in this thread like on page 30, that you can change it inside the docker, but after new update, its away.... ... soooo is there a way to make this thing handle 1 person at a time (Handy+PC) without changing config after every update? Like a variable in the template i could use? I dont use SSL or reverse proxy, but mariadb. Is there anything i can do to increase speed besides the FPM thingy? Login takes forever, uploads sometimes also... downloads also... What could This be?

Okay, log purge does seem to work also for nodes, thanks! For clarification, i just use this node mode since some days on one node, to test it. "1" seem to be more then 1 day, but that doenst matter as long as it gets automatic deleted from time to time... Good work. For automated building: https://docs.docker.com/docker-hub/builds/#create-an-automated-build

Thanks ill try first just adding the variable I also changed your repo to zugz/r8mystorj:latest Okay, works, atleast for the main node - does it work for storj10\Node_1\log? - i dont have old enaught files to test I just wonder, because while i had the other storj docker, i got an update every day, now not anymore, did i forget anythign!?

Yea, you are right, specific "standard" options should be included via OS not via plugins. But that is how it is.

Hi, you asked for diagnose log, here it is. I think it startet 1.5 4:40 where all dockers just goin to disabled state. Was it because of parity check? (but i never notcied this) unraid-server-diagnostics-20180502-1257.zip I have this plugin currently not installed, because of 2 times where some or all docekrs were closed, which were running fine before i installed this plugin. Edit: I just let it autostart every docker, and let ip at 192.168.0.2 (if i remember correctly thats what it defaults to?) and no port given, at time i entered 1 for the first and then something like 10 for the next, the latest has something like 30 sec cooldown.

@jcloud THANK YOU! But the change is not pushed by now?! Seems like "much traffic" yesterday to today. Im already at ~11mb

Yes, for me its working, i just needed to change that Key in the template. U can see my nodes when u enter "unraid" in the ranking (while tryin storjmonitor running, i accidently deleted my first storj node which had over 100GB :() Im just waiting for the point they start selling their service again so new customers may lay their files there, until then, its just "farming" for reputation and response time getting low... and waiting for it to start...

Hm thats mysterios, but i also can confirm that my dates in the dockers are sometimes not that acurat (like hours off) - but no problems - and usually at some point the nodes goes normal again... If im right it can go -300 - +300 without problems, above, below is a problem.

Guys, the last weeks was much traffic because it was trash test data. Now its back to normal. Test was from (i dont know) till 27.4... I got like 5mb the last couple days, that is normal. (11 nodes) I posted a log checker, use this if u unsure if your nodes are running okay. This docker works perfect, i only needed to adjust the ports of the extra nodes created if you use this feature.

Hows ur delta?

Read before, i wrote that already

Yeah, i know that. Thats why i could easy check how big my log dir is. But if you want to make it perfect you could make the +1 a variable, with standard 30. This way you have 1 variable to enable delete and one variable where every user could say if delted after 1...2...3..or 60 days... Also, i dont care about 100gb more or less, like you, but just think about it at some time you forget the storj containers and its getting more and more... like in a year 1000gb...^^

Hey, in my mind its not deleting from unraid host. Isnt entrypoint only run inside the docker and /storj/log is also only inside the docker? My log dirs are different in size, but i think about 10gb in not a month, without my big node which i deleted and was 3 months old. U can easy change +1 to +30 to delete 30 days old data. I dont really think the log files are improtant, because you could also set it to no logging at all. Log files are so easy to modify i really hope storj is not relayin on them for anything

Okay, now i really now it works all. My first stored MB since i tried to install storjmonitor... Now we only need to fix the logs directory and then its perfect. My suggestion for the deleting of the log file would be: if [ -n "${DELETE_LOG}" ]; then sleep 10; find /storj/log -iname "*" -mtime +1 -delete fi And we just add a key DELETE_LOG to the template and when its there it deletes logs older then 1 day. I cant think why you dont want this, but if someone dont want it, he just removes the DELETE_LOG from the template and finish. I testet find /storj/log -iname "*" -mtime +1 -delete and it works inside the storj container. Removed over 300mb in jsut one storj instance.. We could also do a "if the dir is there" instead, but i guess, it doenst matter at the end.

No problem! Im glad u know what i mean now... i guess your log files are also getting big?

Did you change this? And yes im refering to the stroj/log folders

I found out why its not working. In template you name your storjmonitor key "MONITORKEY", but in entrypoint its: if [ -n "${STORJ_MONITOR_API_KEY}" ]; then sleep 10; sed -i "s/YOUR-TOKEN-HERE/${STORJ_MONITOR_API_KEY}/" /opt/StorjMonitor/storjMonitor.js; cd /opt/StorjMonitor; (/opt/StorjMonitor/storjMonitor.sh &) & i guess you need to change MONITORKEY to STORJ_MONITOR_API_KEY or remove the "if" Edit: Yes it works, you need to change MONITORKEY in template to STORJ_MONITOR_API_KEY...., then its filling in the correct API Key. Its because that IF checks if this key is there, and dont start storjmonitor when the key is not there... While you at it, you could add (or a working code) logs=$(find /storj/log/ -name '*.log');for log in $logs; do cat /dev/null > $log;done to the entrypoint script (dont work for me, i dont know why :()

btw, i found https://ssdynamite.com/ there you can check your log files of storj if there is any problem... seems like all instances are working.

For log deleting im using But i also tried yoru script via ssh, still there are logs in the storj containers...?! As far as i understand these logs has to be deleted from within the container!?

Hmm.. im confused some minutes ago all my dockers updated... and storj monitor is complete removed... With the replacement i understand what you mean, but your script is broken at this point (atleast for me) the last version try to change YOUR KEY HERE to my key, but there was not YOUR KEY HERE in your original file, you understand? Im also wondering i dont get any new MBs since i switched to your new template... i wonder if storj itself is working correctly. And now after update, all storj monitor is missing..

It seems the only thing you need to change now is: 1.) Make sure YOUR KEY HERE is in your original storjmonitor.js so your entrypoint script can cahnge it to the correct api key, besides this, it seems to work just fine! or change and dont look for YOUR KEY HERE, but for your api key "H8WvafR710FPK2zA4ZTd7NTX24HsGB5xc9curODs" and let it get changed to the real api key. 2.) let it delete the log folder (or the files in it) automatic (maybe just always on restart, or if its X days old.)

I cant write more without writing in red, so new thread... / # ls -l total 12 drwxr-xr-x 1 root root 218 Apr 26 09:45 StorjMonitor drwxr-xr-x 1 root root 808 Jan 9 19:36 bin drwxr-xr-x 5 root root 340 Apr 26 09:45 dev -rwxrwxrwx 1 root root 2016 Apr 19 07:10 entrypoint drwxr-xr-x 1 root root 530 Apr 24 13:31 etc drwxr-xr-x 1 root root 0 Jan 9 19:36 home drwxr-xr-x 1 root root 222 Jan 9 19:36 lib lrwxrwxrwx 1 root root 12 Jan 9 19:36 linuxrc -> /bin/busybox drwxr-xr-x 1 root root 28 Jan 9 19:36 media drwxr-xr-x 1 root root 0 Jan 9 19:36 mnt dr-xr-xr-x 580 root root 0 Apr 26 09:45 proc drwx------ 1 root root 56 Apr 26 09:43 root drwxr-xr-x 1 root root 0 Jan 9 19:36 run drwxr-xr-x 1 root root 766 Jan 9 19:36 sbin drwxr-xr-x 1 root root 0 Jan 9 19:36 srv drwxrwxrwx 1 99 users 16 Apr 24 12:05 storj dr-xr-xr-x 13 root root 0 Apr 26 09:45 sys drwxrwxrwt 1 root root 64 Apr 19 05:31 tmp drwxr-xr-x 1 root root 46 Apr 19 05:31 usr drwxr-xr-x 1 root root 78 Jan 9 19:36 var -rw-rw-rw- 1 root root 152 Apr 19 06:25 versions / # cd storj /storj # dir /bin/sh: dir: not found /storj # ls -l total 8 -rw-rw-rw- 1 99 users 3062 Apr 24 14:01 config.json -rw-rw-rw- 1 99 users 3062 Apr 24 14:01 config.json.bak drwxrwxrwx 1 99 users 108 Apr 26 00:00 log drwxrwxrwx 1 99 users 68 Apr 24 12:03 share /storj # Could it because of wrong rights? If so, you could add "set correct rights" at startup part? For my part, i dont need everything setup in template, i would rather set the correct values in the conf, so i know its working all correctly... Also, for me, in your entrypoint file, but i could have no idea about it, it seems like you dont use variables for ports? How does it even work? sed -i "s/YOUR-TOKEN-HERE/${MONITORKEY}/" /StorjMonitor/storjMonitor.js; mkdir -pv "${DATADIR}/share" "${DATADIR}/log"; if [ ! -f "${DATADIR}/config.json" ]; then storjshare create --storj "${WALLET_ADDRESS}" --storage "${DATADIR}/share" --size "${SHARE_SIZE}" --rpcport 4000 --rpcaddress "$ (later ports also no variable) What i can confirm, if you install it with your docker, you dont set YOUR-TOKEn-HERE in storjmonitor.js, so your script cant find that point and all dockers created with this use wrong api key... if i set YOUR TOKEN HERE, the api key g ets replaced just fine. (but still not working) - only manual. I would suggest to publish this container first without variables, just config files which needs to be edited (like you can access atm storj conf, but not storjmonitor from outside of docker) I also wonder why i cant use apt-get in the docker, shouldnt this all be installed via the install script? I also cant "find" (inside the docker) the daemon.log which storjmonitor should create... EDIT: okay some nodes seem to work and report their size correctly, i just edited the storjmonitor.js and replaced the key with mine. Ill try to find out if all work or what i have done other then on others (like if its needed to +x it) Edit2: GOOD NEWS! It seems to10 from 11 nodes are working, it doesnt matter if u +x it. U just need to replace the key in the conf. If you want to keep the variables, then you need to make sure that ur original storjhmonitor.js has actually YOUR_KEY_HERE in it. So the replacement works. Edit3: Seems like all 11 nodes are running fine now. Its just confusing because you get invalid farmer data and or error (and it works 15 min later on his own) (i guess there are a max 1 connection per 15 min setting on their server or something)

ITS WORKING. CALL ME GOD! 1.) Ur script doesnt seem to enter the API key correct. Make sure YOUR KEY HERE is in your original storjmonitor.js (its not in mine when i install from your template, its your key in there for me, every time) 2.) (Also it might be that ur scritp doenst set chmod +x? (executable?))? [doenst needed see last post] 3.) could u implement a "if share diretory = 0 bytes" dont open storjmonitor? (would reduce false positives) 4.) please add a "delete /log/" after X days or after X mbs You can skip the rest until the last post last words... It said var token = "H8WvafR710FPK2zA4ZTd7NTX24HsGB5xc9curODs"; (where does it get that from!?) I just "vi"ed it and changed it with my real api key... and ... /StorjMonitor # vi storjMonitor.js /StorjMonitor # ./storjMonitor.js /bin/sh: ./storjMonitor.js: Permission denied /StorjMonitor # chmod +x storjMonitor.js /StorjMonitor # ./storjMonitor.js [09:33:01] 5e2ce75d9e5d679d125eb2a2228c987f2f236a61 | Submit to Storjstat [09:33:02] 5e2ce75d9e5d679d125eb2a2228c987f2f236a61 | Success It also appears on the website finally.. THANK YOU FOR YOUR HELP! AND YOUR SCRIPTS! AND YOUR TIME! Now just one last question... when the docker gets updated, does this changes vanish? (the correct api key?) edit: It seems like its just manually working, in log still: * starting node with config at /storj/config.json{"level":"info","message":"got status query","timestamp":"2018-04-26T09:45:24.250Z"}[09:45:24] 6dd89bb44f8b72ed5cfe5be5f506161b8dac5b3f | Submit to Storjstat[09:45:24] ERROR {"error":"Invalid farmer data (spaceUsedBytes)"}

Till now: (storj) 1 fresh new install with ur new docker - some reputation gained, but no files stored so far, so it makes sense that storjmonitor is not working (storj1) 1 fresh install and then (stop) and copy old files over - i guess here it should report files stored, but didnt do 9 other nodes with just "old files with new docker" none of them show any data till now, (for storj1-10) im also concerned if they work correct, because i get many timeouts in log... also no increase in reputation.. but timeout goes down...?! BTW, while were at logs... in all of my dockers the log directory get bigger and bigger, could u implement an simple startup script which deleted logs after 3 days (or something like this?) Currently i have about 10GB of logs in my 11 nodes