Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Permission problems on QNAP #2

Closed
balli1187 opened this issue Jun 7, 2022 · 8 comments
Closed

Permission problems on QNAP #2

balli1187 opened this issue Jun 7, 2022 · 8 comments

Comments

@balli1187
Copy link

Dear Philipp,

I came accross your work and love the idea. Thanks for sharing!

I tried to run it on my QNAP NAS with a Docker-compose file but it rans into permission problems (see the log I copied from portainer):

Allowing use of questionable username. Adding user NAS' ...
Adding new group NAS' (1000) ... Adding new user NAS' (1000) with group NAS' ... Creating home directory /home/NAS' ...
Copying files from /etc/skel' ... sh: 1: cannot create /etc/opt/brother/scanner/brscan4//brsanenetdevice4.cfg: Permission denied

Unfortunately I was not able to sold it myself. I couldn't find the script/line in a script that causes the problem.
Can you help?

Regards Stephan

@PhilippMundhenk
Copy link
Owner

I can't seem to reproduce the error and am a little short on time these days. Lets try a quick fix: You might want to try adjusting files/runScanner.sh and after env > /opt/brother/scanner/env.txt (line 4) add

mkdir -p /etc/opt/brother/scanner/brscan4/
chmod -R 777 /etc/opt/brother

Let me know if that helps...

@balli1187
Copy link
Author

Hi,

Thanks for reply.
I added the lines in runScanner.sh and rebuild the Container but doesn't change anything.

I'm not so experienced in this stuff but is it right that there is a double slash in the dir that causes permission problems?
It looks unfamiliar to me, that's why I'm asking.

@PhilippMundhenk
Copy link
Owner

PhilippMundhenk commented Jun 9, 2022

Hi @balli1187,
alright, I managed to update the drivers to the newest version, build the container, reproduce, and seemingly fix the error. I updated this repository. Please try to pull it again, rebuild, and recreate the container and see if it works now.

The double slash is no issue. It is also created by the Brother drivers, so not much of a handle there. I tried to circumvent some seemingly wrong things, so would be interesting to know if everything still works...

@PhilippMundhenk
Copy link
Owner

PhilippMundhenk commented Jun 9, 2022

Found an even better fix, make sure to grab the latest version and let me know how it goes!

@balli1187
Copy link
Author

Thanks for the fix.
Now the container comes up ending wirh"startup successful" message.

Unfortunately I can not scan to my NAS. Tried
Scanner -> Scan-to-PC -> File
But the printer shows "no computer found".

Any suggestions how to fix it?
Which protocols are needed to? I disabled SNMP in the initial setup cause I didn't know it will be used.

@PhilippMundhenk
Copy link
Owner

My apologies, this topic has completely dropped off my radar.

Yes, I added this message to make sure all init works well. So we fixed the first error it seems.

Not quite sure where the second one is coming from, I will try to reproduce. SNMP is definitely reqired though for the connection of the buttons, so this might already be an issue. You might want to keep this active.

@balli1187
Copy link
Author

Everything is fine, no need for excuse.

I figured it out myself: I changed the User that runs the container und that causes new permission problems. After changier the script's owner everything worked.

I have tried some things to reduce the size of the pdfs as my first scan needed 30mb for 4 sheets.
I'm now converting all pnm-files to jpeg before the pdf conversion starts.

Next step will be ocr and it would be really interested in that automatic correction that you mentioned in your blog.

@PhilippMundhenk
Copy link
Owner

Excellent, I will close this ticket now.

But here are some pointers to the items you raise:

PhilippMundhenk pushed a commit that referenced this issue Nov 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants