After spending the last couple hours trying to figure out why the event console wasn’t showing up in my manually upgraded OMD/check_mk install (that is OMD 1.2 w/ check_mk 1.2.4p5 upgraded to 1.2.6b10) even though mkeventd is running – here’s what you got to do: manually copy the files from your check_mk source directory into the install director. The setup script does everything else for your, except that.
cd ~ cd check_mk-1.2.6b10/mkeventd.src rsync -av web/* ~/local/share/check_mk/web/ sending incremental file list htdocs/ htdocs/mkeventd.py htdocs/images/button_mkeventd_hi.png htdocs/images/button_mkeventd_lo.png htdocs/images/icon_ack.png htdocs/images/icon_clear.png htdocs/images/icon_counting.png htdocs/images/icon_delayed.png htdocs/images/icon_mkeventd.png htdocs/images/icon_resetcounters.png plugins/ plugins/config/ plugins/config/mkeventd.py plugins/icons/ plugins/icons/mkeventd.py plugins/sidebar/ plugins/sidebar/mkeventd.py plugins/views/ plugins/views/mkeventd.py plugins/visuals/ plugins/visuals/mkeventd.py plugins/wato/ plugins/wato/mkeventd.py sent 210,421 bytes received 346 bytes 421,534.00 bytes/sec total size is 209,125 speedup is 0.99
That’s it. WATO should now show the event console again and things like rule based notification will also work.
Hi,
can you please write more details to do this?
Thanks,
Oliver
This fixed it! Thank You!
(had to do an omd restart after, but that’s to be expected)
Also, I had a similar issue, manually upgrading to 1.2.6p5. Chrome’s developer console was reporting that most of the CSS and JS files were not loading (404 errors). Went into !/local/share/check_mk/web/htdocs and created symlinks for all the .css files there. Then did the same in the js folder for all the .js files. All seems to be happy there now.