Jump to content
Squid

[Plugin] CA Fix Common Problems

1100 posts in this topic Last Reply

Recommended Posts

Fixed all the suggested common problems -- down to three and all are the same thing -- enable auto update. When I click on the button I can see it is taking me to http://tower/Settings/AutoUpdate but nothing loads, I also don't have anything called AutoUpdate in Settings.

 

Is autoupdate a plugin that needs to be installed?

 

If yes then it would probably be useful to check for that and generate a problem if it is not installed.

Community Applications is not up to date from when that got added to it (2016/04/17).  You got caught in an almost catch-22 situation.  You probably enabled plugin notifications to be set, but the dynamix checks for updates available hasn't run yet, so CA being out of date hasn't been logged yet.

 

 

 

Share this post


Link to post

Fixed all the suggested common problems -- down to three and all are the same thing -- enable auto update. When I click on the button I can see it is taking me to http://tower/Settings/AutoUpdate but nothing loads, I also don't have anything called AutoUpdate in Settings.

 

Is autoupdate a plugin that needs to be installed?

 

If yes then it would probably be useful to check for that and generate a problem if it is not installed.

Community Applications is not up to date from when that got added to it (2016/04/17).  You got caught in an almost catch-22 situation.  You probably enabled plugin notifications to be set, but the dynamix checks for updates available hasn't run yet, so CA being out of date hasn't been logged yet.

 

Thank you -- all fixed

Share this post


Link to post

- Fixed (better be) Crashplan webUI

 

All fixed :)  Thanks!

 

Sounds promising :)

 

I'll be away from my server for quite some time, but given that your WebUI snippets looked extremely familiar I'm sure it is solved now.

Share this post


Link to post

I feel like I'm waiting for something that isn't going to happen

 

- Check for CPU Throttling driver installed

- Check for docker apps extra parameters set via repository (old style) instead of via extra parameters (Old style messes up updates of apps)

- Ability to not log ignored faults

Share this post


Link to post

Too much time on my hands, or the appropriate skills to not need much time?

 

One of the problems with misconfigured docker apps is that they *may* write to your array media files with vastly different ownerships / permissions than what unRaid expects to operate normally (ie: the Windows error you need permission from root to perform this operation)

 

The New Permissions tool included with unRaid is great for fixing these problems, but if it runs against your appdata folder(s) then it can wreck havoc with the docker apps themselves and cause them to be non-functional.

 

With this update, a Docker Safe New Permissions tool will show up under Tools which will automatically scan your containers (and if you're on 6.2 your default appdata location) to determine which shares should not have their permissions set back to default, and skip those shares.

Share this post


Link to post

- Check for CPU Throttling driver installed

 

Tested with and without driver - works well.  Thanks!  Now to see if anyone else besides me has the problem!

Share this post


Link to post

This just picked up a couple of issues for me.

 

Incorrect permissions on one folder - fixed with the docker-safe new perms util

 

Hadn't notice Ubooquity had changed the default port.

 

Good Work Squidly!  ;D

Share this post


Link to post

Hello!

 

I'm having a small problem,  share "Backup" says it has files on the cache but cache is disabled on that folder (it used to be enable a few days back), so not sure if it's false positive but something is not quite right.

5pS0vBy1+

 

 

But going to the share list there's no files in the cache, all are on Disk2. Also tried executing the Mover but there's nothing to move

5KG6oIdY+

 

Thanks for any info!

Share this post


Link to post

Hello!

 

I'm having a small problem,  share "Backup" says it has files on the cache but cache is disabled on that folder (it used to be enable a few days back), so not sure if it's false positive but something is not quite right.

5pS0vBy1+

 

 

But going to the share list there's no files in the cache, all are on Disk2. Also tried executing the Mover but there's nothing to move

5KG6oIdY+

 

Thanks for any info!

I know I made the reverse test more permissive but can't remember if I made this one the same.  Basically at the very least that folder exists on the cache drive.  If that's the only thing causing it to fail then I'll adjust the code

 

Sent from my LG-D852 using Tapatalk

 

 

Share this post


Link to post

Hello!

 

I'm having a small problem,  share "Backup" says it has files on the cache but cache is disabled on that folder (it used to be enable a few days back), so not sure if it's false positive but something is not quite right.

5pS0vBy1+

 

 

But going to the share list there's no files in the cache, all are on Disk2. Also tried executing the Mover but there's nothing to move

5KG6oIdY+

 

Thanks for any info!

I know I made the reverse test more permissive but can't remember if I made this one the same.  Basically at the very least that folder exists on the cache drive.  If that's the only thing causing it to fail then I'll adjust the code

 

Sent from my LG-D852 using Tapatalk

 

Thanks for your quick reply, Squid. Indeed, you were right. I didn't realise there was a /mnt/cache/Backup folder. Deleted it and now I don't get the warning anymore.

 

Thanks!

Share this post


Link to post

Not sure if this has been reported in the last 14 pages but I'm getting this little quiky warning

 

The webUI the author specified is http://[iP]:[PORT:8096]/ and the webUI you are using is http://192.168.1.10:8096/.
If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues
should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP
address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the
container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the
application. You can fix this problem here

 

I'm a tad confused :)

Share this post


Link to post

Not sure if this has been reported in the last 14 pages but I'm getting this little quiky warning

 

The webUI the author specified is http://[iP]:[PORT:8096]/ and the webUI you are using is http://192.168.1.10:8096/.
If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues
should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP
address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the
container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the
application. You can fix this problem here

 

I'm a tad confused :)

99.999% of the time there is never a reason to change the author's webUI entry

 

You are specifying an absolute IP address, and an absolute PORT number

 

The Author specified this:  http://[iP]:[PORT:8096]/

 

What this means is that unRaid will take whatever its IP address is and replace [iP] within it, and whatever host port is currently mapped to container port 8096 and replace [PORT:8096] with it

 

What you've done is change that line and did unRaid's job for itself by using http://192.168.1.10:8096/

 

This is a warning because what you're doing works. (and warnings can be set to not send notifications)

 

But consider two scenarios:

 

You replace your modem / router, and its using a different subnet of 192.168.2.x  Now you have to adjust your webUI.  If it was still stock you wouldn't have to

 

If for some reason you decide to change the communication port from 8096 to something else, no you have to adjust the template in 2 places.  If the line was stock, you wouldn't have to.

Share this post


Link to post

Heh, serves me right for thinking http://[iP]:[PORT:8096]/ were placeholders that I needed to substitute with real values.

 

Thanks.  Reverted back to http://[iP]:[PORT:8096]/ and it's still working. Thanks.

Share this post


Link to post

Not sure if this has been reported in the last 14 pages but I'm getting this little quiky warning

 

The webUI the author specified is http://[iP]:[PORT:8096]/ and the webUI you are using is http://192.168.1.10:8096/.
If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues
should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP
address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the
container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the
application. You can fix this problem here

 

I'm a tad confused :)

99.999% of the time there is never a reason to change the author's webUI entry

 

You are specifying an absolute IP address, and an absolute PORT number

 

The Author specified this:  http://[iP]:[PORT:8096]/

 

What this means is that unRaid will take whatever its IP address is and replace [iP] within it, and whatever host port is currently mapped to container port 8096 and replace [PORT:8096] with it

 

What you've done is change that line and did unRaid's job for itself by using http://192.168.1.10:8096/

 

This is a warning because what you're doing works. (and warnings can be set to not send notifications)

 

But consider two scenarios:

 

You replace your modem / router, and its using a different subnet of 192.168.2.x  Now you have to adjust your webUI.  If it was still stock you wouldn't have to

 

If for some reason you decide to change the communication port from 8096 to something else, no you have to adjust the template in 2 places.  If the line was stock, you wouldn't have to.

 

It's a pain for those of us that reverse proxy stuff....  ;D

 

rKRwMEG.png

Share this post


Link to post

Not sure if this has been reported in the last 14 pages but I'm getting this little quiky warning

 

The webUI the author specified is http://[iP]:[PORT:8096]/ and the webUI you are using is http://192.168.1.10:8096/.
If you are specifying an absolute port (IE: PORT:xxxx is missing from your specified webUI address, then you will have issues
should you ever have to change the host port on the docker applications's settings. In the same vein, specifying an absolute IP
address in the webUI will cause issues should your server's IP address ever change. Note that the PORT:xxxx refers to the
container's port, not the host port. There may however be perfectly valid reasons to change the default webUI entry on the
application. You can fix this problem here

 

I'm a tad confused :)

99.999% of the time there is never a reason to change the author's webUI entry

 

You are specifying an absolute IP address, and an absolute PORT number

 

The Author specified this:  http://[iP]:[PORT:8096]/

 

What this means is that unRaid will take whatever its IP address is and replace [iP] within it, and whatever host port is currently mapped to container port 8096 and replace [PORT:8096] with it

 

What you've done is change that line and did unRaid's job for itself by using http://192.168.1.10:8096/

 

This is a warning because what you're doing works. (and warnings can be set to not send notifications)

 

But consider two scenarios:

 

You replace your modem / router, and its using a different subnet of 192.168.2.x  Now you have to adjust your webUI.  If it was still stock you wouldn't have to

 

If for some reason you decide to change the communication port from 8096 to something else, no you have to adjust the template in 2 places.  If the line was stock, you wouldn't have to.

 

It's a pain for those of us that reverse proxy stuff....  ;D

 

rKRwMEG.png

You see that little button that says "IGNORE"?  Magical things happen when you press it...

 

Also, if you're not on the latest version, then upgrade as you'll have more options on how to deal with ignored items and logging, etc

Share this post


Link to post

You see that little button that says "IGNORE"?  Magical things happen when you press it...

 

Also, if you're not on the latest version, then upgrade as you'll have more options on how to deal with ignored items and logging, etc

 

Oh, I've been ignoring it for ages, just trying to annoy you....  ;D

Share this post


Link to post

Hi

Thanks for this plug in. It flagged up a couple of issues.

 

I get this in red in the log file

Jun 14 12:45:04 xeon logger: Fix Common Problems: root 21532 0.1 0.0 449552 19096 ? Sl 12:07 0:03 /usr/bin/docker -d -p /var/run/docker.pid --log-level=error --storage-driver=btrfs

 

I had 2 x ssds but I was getting errors. I swapped back to one SSD and XFS.

 

Is this a result of changing back to XFS/

 

KRs

 

Lee

Share this post


Link to post

Hi

Thanks for this plug in. It flagged up a couple of issues.

 

I get this in red in the log file

Jun 14 12:45:04 xeon logger: Fix Common Problems: root 21532 0.1 0.0 449552 19096 ? Sl 12:07 0:03 /usr/bin/docker -d -p /var/run/docker.pid --log-level=error --storage-driver=btrfs

 

I had 2 x ssds but I was getting errors. I swapped back to one SSD and XFS.

 

Is this a result of changing back to XFS/

 

KRs

 

Lee

Either give me the diagnostics or something like 20 lines before and after.  That line by itself doesn't make sense to me

 

Sent from my LG-D852 using Tapatalk

 

 

Share this post


Link to post

A very minor point - you added a message to the popup to indicate all drives would spin up, a good idea at the time.  Then you added the option to only test spun up drives, another good idea, which I have enabled.  All of my drives are generally always spun down, and stay that way, but we still see the message about all drives being spun up.  Perhaps it could be removed or altered, conditionally?

Share this post


Link to post

Was merely waiting to see how long it took anyone to notice. ????

 

Sent from my LG-D852 using Tapatalk

 

 

Share this post


Link to post

Was merely waiting to see how long it took anyone to notice. ????

 

What's my prize?  (If the deadline is past, I actually saw it a week or 2 ago!)  :D

Share this post


Link to post

Was merely waiting to see how long it took anyone to notice. ????

 

Sent from my LG-D852 using Tapatalk

I call bull5#1+ on that one....

Share this post


Link to post

Was merely waiting to see how long it took anyone to notice. ????

 

Sent from my LG-D852 using Tapatalk

I call bull5#1+ on that one....

Fair enough.  How about this:  I was just too lazy to fix it

 

Sent from my LG-D852 using Tapatalk

 

 

Share this post


Link to post

Was merely waiting to see how long it took anyone to notice. ????

 

Sent from my LG-D852 using Tapatalk

I call bull5#1+ on that one....

Fair enough.  How about this:  I was just too lazy to fix it

 

Sent from my LG-D852 using Tapatalk

That sounds a bit more like the Squid we know and love....

Share this post


Link to post

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.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.