Bug #3450
Ntopng fails to start after upgrade
Status: | CLOSED | Start date: | ||
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 100% | |
Category: | nethserver-ntopng | |||
Target version: | v6.10 | |||
Security class: | Resolution: | |||
Affected version: | v6.10 | NEEDINFO: | No |
Description
The Ntopng daemon fails to start after the upgrade tool runs.
- When a logical interface is created, the ntopng configuration could break (see #3447)
- Once upgraded to ns7 this error is displayed if the ntopng process is started from the command line:
*** FATAL CONFIG FILE ERROR *** Reading the configuration file, at line 7 >>> 'logfile /var/log/redis/redis-ntopng.log' Can't open the log file: Permission denied
Workaround
chown -c redis.redis /var/log/redis/redis-ntopng.log
Associated revisions
Fix post-upgrade ntopng startup error
Refs #3450
History
#1 Updated by Davide Principi over 2 years ago
- Description updated (diff)
- Status changed from NEW to TRIAGED
- % Done changed from 0 to 20
#2 Updated by Davide Principi over 2 years ago
- Assignee deleted (
Davide Principi)
In nethserver-testing 6.10
- nethserver-upgrade-tool-1.0.0-1.11.gbc26615.ns6.x86_64.rpm
#3 Updated by Davide Principi over 2 years ago
- Status changed from TRIAGED to MODIFIED
- % Done changed from 20 to 60
#4 Updated by Davide Principi over 2 years ago
- Status changed from MODIFIED to ON_QA
- % Done changed from 60 to 70
#5 Updated by Davide Principi over 2 years ago
- Status changed from ON_QA to VERIFIED
- % Done changed from 70 to 90
VERIFIED
#6 Updated by Davide Principi over 2 years ago
- Status changed from VERIFIED to CLOSED
- % Done changed from 90 to 100
In nethserver-updates 6.10:
- nethserver-upgrade-tool-1.1.0-1.ns6.x86_64.rpm