David Rajendra
2017-07-03 12:27:36 UTC
Hello xCAT users,
I am using this version of xCAT:
# lsxcatd -v
Version 2.13.2.POST111.gbdd8e64 (git commit 06d7097f42eca03db70c9eb93b8abeaf8ca1c2be, built Thu Jun 8 14:21:16 UTC 2017)
I noticed since I upgraded to 2.13.2 that xCAT is no longer writing output from my postscripts to /var/log/xcat/xcat.log on the node but only the start/end of each postscript.
Example:
[edited]
running /xcatpost/mypostscript.post
Fri Jun 30 18:05:12 CEST 2017 Running postbootscript: otherpkgs
Fri Jun 30 18:07:39 CEST 2017 postbootscript otherpkgs return with 16
Fri Jun 30 18:07:40 CEST 2017 Running postbootscript: postscriptA
Fri Jun 30 18:10:58 CEST 2017 postbootscript postscriptA return with 0
Fri Jun 30 18:10:58 CEST 2017 Running postbootscript: postscriptB
Fri Jun 30 18:10:58 CEST 2017 postbootscript postscriptB return with 0
Fri Jun 30 18:27:30 CEST 2017 Running postbootscript: reboot
Fri Jun 30 18:27:30 CEST 2017 postbootscript reboot return with 0
/xcatpost/mypostscript.post return
On xCAT 2.12.2 this was giving more useful output.
Why has the code been changed ?
I found it much quicker to debug having my postscript output written to the local node /var/log/xcat/xcat.log rather than it being sent by to syslog.
One of my colleagues noted that a code a change had been made "Fix double logging of postscript output in /var/log/xcat/xcat.log" in 2.13.2.
If this is such a problem could we not have a setting to turn this on or off instead ?
I would prefer that the change be reverted.
Regards,
David
I am using this version of xCAT:
# lsxcatd -v
Version 2.13.2.POST111.gbdd8e64 (git commit 06d7097f42eca03db70c9eb93b8abeaf8ca1c2be, built Thu Jun 8 14:21:16 UTC 2017)
I noticed since I upgraded to 2.13.2 that xCAT is no longer writing output from my postscripts to /var/log/xcat/xcat.log on the node but only the start/end of each postscript.
Example:
[edited]
running /xcatpost/mypostscript.post
Fri Jun 30 18:05:12 CEST 2017 Running postbootscript: otherpkgs
Fri Jun 30 18:07:39 CEST 2017 postbootscript otherpkgs return with 16
Fri Jun 30 18:07:40 CEST 2017 Running postbootscript: postscriptA
Fri Jun 30 18:10:58 CEST 2017 postbootscript postscriptA return with 0
Fri Jun 30 18:10:58 CEST 2017 Running postbootscript: postscriptB
Fri Jun 30 18:10:58 CEST 2017 postbootscript postscriptB return with 0
Fri Jun 30 18:27:30 CEST 2017 Running postbootscript: reboot
Fri Jun 30 18:27:30 CEST 2017 postbootscript reboot return with 0
/xcatpost/mypostscript.post return
On xCAT 2.12.2 this was giving more useful output.
Why has the code been changed ?
I found it much quicker to debug having my postscript output written to the local node /var/log/xcat/xcat.log rather than it being sent by to syslog.
One of my colleagues noted that a code a change had been made "Fix double logging of postscript output in /var/log/xcat/xcat.log" in 2.13.2.
If this is such a problem could we not have a setting to turn this on or off instead ?
I would prefer that the change be reverted.
Regards,
David