Summary: | upon fresh Guardian install, configuration files not created | ||
---|---|---|---|
Product: | IPFire | Reporter: | Rod Rodolico <rodo> |
Component: | --- | Assignee: | Stefan Schantl <stefan.schantl> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | Major Usability | ||
Priority: | - Unknown - | CC: | michael.tremer |
Version: | 2 | ||
Hardware: | other | ||
OS: | Unspecified | ||
Attachments: |
grep of http error log for this problem
Perl Script to generate a series of Unix commands to sync permissions on affected machine bash script which does a partial recovery from the installation |
Description
Rod Rodolico
2016-07-16 05:38:39 UTC
Created attachment 455 [details]
Perl Script to generate a series of Unix commands to sync permissions on affected machine
Created attachment 456 [details]
bash script which does a partial recovery from the installation
Ok, it is definitely a permissions issue, as researched by Matthias and probably others. The "installation" sets ownership of everything to user 1000, group 1000, which on my system is samba:samba.
The attached perl script, when run on another firewall, will determine the correct permissions and generate command useful for a bash script (or copy/paste) to return the system to its correct setup. The bash script is an output of the same, but one which did not have Guardian installed, so it does not fix the permissions on those directories.
Hello Rod, thanks for pointing this out. The problem was an permission issue during creating the test package. I've repacked the latest test version with correct ownership and permissions and uploaded the packages. Just download the package again and install it the usual way. -Stefan |