Cessquill

I've gone through and set v3 up, and I'm having a problem. Asking here first since Google doesn't return much (which makes me ponder docker issue - probably illogically). Problem: Newsletter Cron settings Actions: Setup, System, Jobs - the Newsletter Cron box is empty, red and has "The Newsletter is required" underneath. All others are fine According to the Wiki, it's supposed to default to 12GMT every Friday, so I've tried entering "0 0 12 ? * FRI *", but I get "CRON Expression 0 0 12 ? * FRI * is not valid". Anybody else having a similar issue?

I had similar when I first upgraded, and now I occasionally get my dockers disappear completely. Restarting the dockers system by going to settings/docker, selecting "no" and saving, then changing it back to "yes" brings things back. Might be worth a try until somebody with proper knowledge drops by - from what I can make out the docker version in this release seems a bit flaky.

Somehow looks to be created in about 59 years time...?

Where exactly can you see 192.168.178.21?

Upgrading docker containers today, and things get stuck on the "stopping container" part. Opened new browser tab to view log and had an upstream timeout message (which has since scrolled off). Tried downloading diagnostics, but that timed out too. Got the diagnostics from the command prompt (attached). Everything else seems to be running OK. Any ideas? unraid1-diagnostics-20180324-1055.zip

The developer of the plugin has not kept it up to date, AFAIK. Remember, plugins and dockers are not necessarily products of Lime Technology, and their continued development and support is unfortunately not guaranteed. I only ever used it to preclear disks before adding them to the array. Once it was pointed out that unRaid can clear a drive without stopping the array I was fine. If people want to stress-test a drive, there are still ways.

Don't wish to offend, but have you restarted your server since upgrading?

Seems to be OK now - think Amazon was having a blip.

Having problems downloading as well. Also having trouble updating dockers

Does the utility take into account the split level of each share? If not, rather than looking at the next level, could it drill down to the correct split level? In your example above, 1st attempt would automatically read the same data as 2nd attempt. Appreciate that might complicate things quite a bit though.

Thanks guys - much appreciated

Really sorry to chime in on this - I've read 4-5 pages back and I just want some assurance... I'm putting another 8TB Ironwolf in my array this evening. Not sure yet whether I'm replacing a drive or adding. First drive change since uninstalling Preclear. I don't need the drive straight away, and can afford to run some extended SMART tests before trusting it. What I can't really afford though is for my Array to be offline for a long time. Can I drop the drive in, format it and add it to the array now?

Thanks for raising this though - I was having the same issue. In Chrome, click the "i" next to the address, select Cookies then Remove. Refresh the page, all should be good

Whilst you wait for proper replies - the preclear plugin is not compatible with 6.4.1 yet (unless it has changed recently)

I'd not see Ombi before - thanks for the tip

Check the two posts above yours.

There's been a few discussions about this, and yes - would be very handy. As drives are getting larger, parity checks are taking longer, and some of us want the ability to do this. IIRC, some of the suggestions were... - Ability to perform percentage of parity check (as you say) - Ability to pause/resume parity check - Only run parity check between certain times, and automatically pause/resume when time is up - Automatically pause parity check when drives are busy - Continuously run parity check automatically (say 5-10%/day?), so when it finishes it starts at the beginning again. Full parity check still available - Others I can't remember

+1 for this - I'd often thought the top right arrow took you to the area the notification was talking about, not closed it (IIRC, older designs had a cross icon to close).

A lot of questions on here (one of which has been mine, and has tripped me up a couple of times) are the "wrong csrf_token" in the logs due to browsers being left open over a reboot. I have a habit of leaving quite a few browsers open here and there and swamping my log. Would a UI update be possible that stores a boot ID/timestamp in the client and periodically polls the server to see if they still match? (I don't know what data is available to the client, but presumably there's something that could identify the current boot without compromising security) Then, if the server has been rebooted, the browser will know by the next ajax call, stop further calls and either... - reload (not sure it's wise) - redirect to a message page - overlay a modal message

Off topic, but I was thinking the other day that it would be great if the UI could detect if it was a stale browser session and either reload or switch screens. It would (theoretically) stop these errors. It could poll the server periodically for a session/boot ID, and if there was a mismatch, it's stale. I'm off to the feature requests area...

It's a known issue: https://github.com/lokenx/plexrequests-meteor/issues/514

Hi - I've suddenly started getting 500 errors when trying to log on. If I'm logged on already I think all is fine. This is in the docker's log... Exception while invoking method 'checkPlexUser' TypeError: Cannot call method 'toLowerCase' of undefined at [object Object].Meteor.methods.checkPlexUser (server/methods/authentication/plexAuthentication.js:69:1) at maybeAuditArgumentChecks (livedata_server.js:1698:12) at livedata_server.js:708:19 at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1) at livedata_server.js:706:40 at [object Object]._.extend.withValue (packages/meteor/dynamics_nodejs.js:56:1) at livedata_server.js:704:46 at tryCallTwo (/app/bundle/programs/server/npm/promise/node_modules/meteor-promise/node_modules/promise/lib/core.js:45:5) at doResolve (/app/bundle/programs/server/npm/promise/node_modules/meteor-promise/node_modules/promise/lib/core.js:171:13) at new Promise (/app/bundle/programs/server/npm/promise/node_modules/meteor-promise/node_modules/promise/lib/core.js:65:3) I'll look a little deeper, since my cache drive filled up the other day and ground the dockers to a halt. But if the above offers any pointers, I'd be grateful. EDIT: this is not the admin login page, that's fine. The user/friend login page is borked. Cheers

D'OH! Apologies. Wasn't thinking straight.

Is there any way of displaying estimated time remaining on the current step when clearing a drive? (either instead of or as well as elapsed)

Hi @Squid - sorry to resurrect this, but I have the same requirement. Are you sure running both would be pointless (I could have missed the point)? I sometimes hit 75% cache capacity quickly, and want to trigger the mover. However, other times there's not a lot of activity. During these quiet times, I'm guessing that anything on the cache could stay there a while - I'd still want to periodically trigger the mover to prevent anything staying cache-only for, long periods (could be a month). At the same time, I don't want the two to interfere with each other by running concurrently (if they would, I don't know). Is there any way the script could be amended to only run if the mover is not already running?