Bug #23038
Directory /var/lib/gwms-frontend/vofrontend/monitor blocks upgrade and reconfig commands
0%
Description
/var/lib/gwms-frontend/vofrontend/monitor should be a symbolic link to /var/lib/gwms-frontend/web-area/monitor
Somehow (I don't know what happened to cause that) on a test machine (fermicloud039.fnal.gov on 8/1/19) a directory got created there and the symbolic link creation was failing, failing every upgrade/reconfig
Probably some mkdir -p (or python equivalent) for a subdirectory created also the directory that was not there because the link had not been created (maybe no upgrade command).
Removing the directory fixed the problem but the error was cryptic:
$ reconfig_frontend -force_name "fermicloud039-fnal-gov_OSG_gWMSFrontend" -writeback no -xml "/etc/gwms-frontend/frontend.xml" -update_def_cfg "no" All connected Factories are at least v3.4.1 usage: reconfig_frontend { -force_name name -writeback yes|no -update_scripts yes|no -xml xml -update_def_cfg yes|no [-xslt_plugin_dir xdir] | -help } Failed to create monitor symlink: [Errno 17] File exists
Why printing the command string?
And the passed test also distracts
At least the messages should be improved.
Maybe the cause of the directory creation found and removed (if the frontend is not configured it should not start)
History
#1 Updated by Marco Mambelli over 1 year ago
- Target version changed from v3_6_1 to v3_6_2
#2 Updated by Marco Mambelli about 1 year ago
- Target version changed from v3_6_2 to v3_6_3
#3 Updated by Marco Mambelli 9 months ago
- Target version changed from v3_6_3 to v3_6_4
#4 Updated by Marco Mambelli 4 months ago
- Target version changed from v3_6_4 to v3_6_5
#5 Updated by Marco Mambelli 4 months ago
- Target version changed from v3_6_5 to v3_6_6
#6 Updated by Marco Mambelli about 2 months ago
- Target version changed from v3_6_6 to v3_6_7