The log server cannot handle a situation with a corrupt filesystem (where the log files are written) in a controlled manner. The problem occures during start up (reboot) and causes a cyclic reboot of the node.
The problem can be re-created in uml environment by setting the directory where the logs shall be written to write protected (> chmod -w repl-opensaf/saflog). This can also be used for test when the problem is solved.
Changed 3 months ago by elunlen
This problem is related to #9 (#3003) and should be solved with #9 (#3003)
Changed 7 weeks ago by elunlen
See also #127 (#3094)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
--- old+++ new@@ -1,3 +1,3 @@The log server cannot handle a situation with a corrupt filesystem (where the log files are written) in a controlled manner. The problem occures during start up (reboot) and causes a cyclic reboot of the node.
-Migrated from devel.opensaf.org #2789+Migrated from devel.opensaf.org #2789 [#124]
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
--- old+++ new@@ -1,3 +1,3 @@The log server cannot handle a situation with a corrupt filesystem (where the log files are written) in a controlled manner. The problem occures during start up (reboot) and causes a cyclic reboot of the node.
-Migrated from devel.opensaf.org #2789 [#124]+Migrated from devel.opensaf.org #2789
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Changed 8 months ago by elunlen
The problem can be re-created in uml environment by setting the directory where the logs shall be written to write protected (> chmod -w repl-opensaf/saflog). This can also be used for test when the problem is solved.
Changed 3 months ago by elunlen
This problem is related to #9 (#3003) and should be solved with #9 (#3003)
Changed 7 weeks ago by elunlen
See also #127 (#3094)
Diff:
Diff:
This problem is fixed with ticket [#9]. However #9 is an enhancement ticket for ver 4.4. Therefore the problem is not fixed for earlier versions.
Related
Tickets:
#9