Usergroup not allowed Tools / All props blacklist randomly

[DigitalSpit]

Occasionally the server will blacklist all props and the only way to remedy this issue is to restart / change the server map (Is it establishing connection to the database?)

Also all of the "users" groups tools will be blocked even though we haven't blocked all of it's tools. Any Help?

[FPtje]

I can't reproduce this issue, so I can't help. This really isn't enough information.

[DigitalSpit]

It's actually all the information I can give you.

Server restarts -> People load in who are in the group "user" -> Cannot use any tools until someone goes into FPP clicks "Group Tool restriction" -> Load groups -> Select user -> Check "Allow all tools by default" this has to be done every server restart, while the other groups remain checked.

[Darklom]

Confirmed the issue of all models blacklisted sometimes, got fixed when server restarted.

[DigitalSpit]

Thank you! @Darklom

[Consequences]

Also experiencing the issue. After every server restart "users" cannot use any toolguns.

Temporary fix: Open Q menu, Utilities Tab, Falco's Prop Protection -> Admin settings, Group Tool Restriction. Load groups, select user. "Allow all tools by default" is checked off. When I uncheck this the issue is fixed. If I choose "Edit selected group's tools" and manually add specific tools they cannot be used until the box is unchecked. Every time the server restarts the box gets rechecked.

This issue should be reopened.

[FPtje]

I need your help to debug this issue. Here's what you have to do

Debugging

1. Get this Lua script: http://pastebin.com/MExwa6gU
2. Put as FPPDebug.lua in the garrysmod/lua directory
3. Enter this in SERVER console: lua_openscript FPPDebug.lua
4. Make sure the script is found etc. It should output some text about FPP. Quite a wall of text. If you don't see a wall of text, you're doing something wrong
5. Go to garrysmod/data/FPP_Debug. You will see one or more files in there.
6. Send those files to me.

I need this data to continue on this bug. No data = no fix.

[FPtje]

People keep reposting the bug over and over again, but they fucking refuse to post the god damn dump https://github.com/FPtje/Falcos-Prop-protection/issues/11

[FPtje]

And if you can't chose between the log from https://github.com/FPtje/Falcos-Prop-protection/issues/8#issuecomment-14631227 or the log from https://github.com/FPtje/Falcos-Prop-protection/issues/11#issuecomment-12184391

I prefer https://github.com/FPtje/Falcos-Prop-protection/issues/8#issuecomment-14631227 I cannot fix this issue if you don't give me these god damn logs.

[FPtje]

No one is replying to this issue anymore. Does that mean it's fixed? Are you having trouble getting the logging thing to work? Did you forget about the issue? Are you too lazy?

I'll close this issue if I don't get a response

[Consequences]

Well, I figured out the issue but one of our admins was an idiot and reinstalled the server before I was able to collect logs or do further testing.

Default behavior of the group tool restriction is a blacklist. We were using it as a whitelist. The check box that flips this logic reset back to checked (specified tools are blacklisted) every time we restarted the server. So, the check box is doing what it is supposed to but the setting isn't persistant between restarts.

It's late tonight but tomorrow I'll fiddle with the checkbox on our test server and see if it still fails to save and if the issue persists I will grab a dump.

[FPtje]

This is not being reproduced.

[brandonjjon]

I'm having the same issue where users connect but can't use any tools. I did the debug: http://pastebin.com/QM1zpLsW

[GovernmentMan]

I know this is a dead thread but this is the only one I have found that talks about this issue. After the server restarts no-one except superadmins can use toolguns. The only way to fix it temporarily is: Open Q menu, Utilities Tab, Falco's Prop Protection -> Admin settings, Group Tool Restriction. Load groups, select NoAccess. "Allow all tools by default" is checked. When I uncheck this the issue is fixed. Every time the server restarts the box gets rechecked.

[FPtje]

@GovernmentMan A regression was fixed on November 24th 2018. Can you confirm you have a version later than that?

Also, if you're running DarkRP, could you run darkrp_check_db_sv in console and check the output?

[GovernmentMan]

Lol honestly I was expecting there to be some large log from whatever command you were to give but I ended up with, "Your sv.db database file is good."

[GovernmentMan]

How do I find the version info?

[FPtje]

When in doubt whether you have the latest version just install latest from GitHub or the workshop. When using DarkRP just make sure DarkRP is up to date and you don't have FPP installed separately.

[CyanFlare]

Hello @FPtje , I'm with @GovernmentMan . The current DarkRP version we are using is the most recent version from the GitHub. We are using FPP that comes with DarkRP.

[FPtje]

What are the settings of the "user" group in FPP? Do you use FAdmin?

[GovernmentMan]

Sorry for the late response. I thought Cyan was taking over the conversation from here since he's the Dev.

We do use FAdmin. Not sure what exactly you mean by settings but I have screencaps of the in-game menu. First one is showing the "Allow all tools by default" box checked on server reset: https://steamuserimages-a.akamaihd.net/ugc/954108744278225062/D026D8A699FF4E2FBEE0615CA8506DDACFF5F996/

Second is the "tools currently in user" on server reset: https://steamuserimages-a.akamaihd.net/ugc/954108744278225291/0D438DDFF3FDA816DDD5181EB058E0E8C6D932AE/

[FPtje]

I think I'll have to join to investigate. Could you mail me with connection details? (fpeijnenburg@gmail.com)

[GovernmentMan]

We would be honored to have you on, I'll get one of the server owners to send you the details. Thank you

[GovernmentMan]

That seems to have fixed the problem, thank you so much!

On Thu, Apr 4, 2019 at 12:12 PM Falco Peijnenburg notifications@github.com wrote:

I think I'll have to join to investigate. Could you mail me with connection details? (fpeijnenburg@gmail.com)

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/FPtje/Falcos-Prop-protection/issues/8#issuecomment-480026481, or mute the thread https://github.com/notifications/unsubscribe-auth/AuYtnoYvYKpf84ZcJEznsUNKhoumsWb7ks5vdk6LgaJpZM4AU3kS .

[FPtje]

Awesome!

[AlohaSteam]

Hi, sorry for re-opening the thread a year later. But I am having the same problem that GovernmentMan was having, I was wondering your solution to it.

[AlohaSteam]

I ran the debug and here is my output https://pastebin.com/HwfwZY37

[FPtje]

Looks like that debug script doesn't work with the latest version of FPP. What happens when you run darkrp_check_db_sv in the server console?

This is assuming you run DarkRP

[AlohaSteam]

"Your sv.db database file is good."

[FPtje]

Well, the good news is that FPP works nothing like how it did when this issue was created. I'm thinking the most likely cause is that some addon is preventing FPP from loading properly and loading the settings. This can happen silently or with an error on startup. Please look in your server console for errors. If you can't find any, try uninstalling addons until the problem is solved.

[AlohaSteam]

There was no error's in console but i do have the addon Prop Control System, do you know of any problems with that addon? Also if its any help you can join the server and i can give you superadmin permissions to mess around with the settings.

[AlohaSteam]

I have found a separate addon for restricting tools, thank you for your support I believe i solved my issue.