All public logs

From Cramsession
Jump to navigationJump to search

Combined display of all available logs of Cramsession. You can narrow down the view by selecting a log type, the username (case-sensitive), or the affected page (also case-sensitive).

Logs
(newest | oldest) View ( | older 50) (20 | 50 | 100 | 250 | 500)
  • 13:44, 13 June 2024 Mflavell talk contribs uploaded File:Matt.jpeg
  • 13:36, 13 June 2024 Mflavell talk contribs created page File:Icon.png
  • 13:36, 13 June 2024 Mflavell talk contribs uploaded File:Icon.png
  • 12:55, 13 June 2024 Mflavell talk contribs created page Installing OneView Monitor on Windows (Created page with "1) Download Apache tomcat & unzip it to a folder. This will be Tomcat's final home - Chose carefully!! 2) Set the JAVA_HOME environment variable. 3) Using the startup file in the tomcat BIN folder start tomcat 4) Access http://127.0.0.1:8080 ensure tomcat is running. If everything is correct you'll see this screen: 5) Using the shutdown script stop tomcat 6) Run the siteminder configuration tool 7) Select "OneView monitor" 8) Provide the path to the tomcat server...")
  • 12:51, 13 June 2024 Mflavell talk contribs created page SMPS does not start after installing Oneview monitor on Linux (Created page with "<h3>Problem:</h3> Site minder sm.registry was updated as ROOT SMPS was starting as SMUSER <h3>Solution:</h3> chown sm.registry to smuser chgroup sm.registry to smuser use find /opt/siteminder -group root to check for root access delete the .pid file restart policy server <h3>Root cause:</h3> Oneview was installed as root NEVER install anything siteminder related as root. During the install of oneview the sm.regitery file was updated as root smps could not read s...")
  • 12:50, 13 June 2024 Mflavell talk contribs created page CA Siteminder (Created page with "[SMPS does not start after installing Oneview monitor on Linux]] <h3>Problem:</h3> Site minder sm.registry was updated as ROOT SMPS was starting as SMUSER <h3>Solution:</h3> chown sm.registry to smuser chgroup sm.registry to smuser use find /opt/siteminder -group root to check for root access delete the .pid file restart policy server <h3>Root cause:</h3> Oneview was installed as root NEVER install anything siteminder related as root. During the install of oneview the...")
(newest | oldest) View ( | older 50) (20 | 50 | 100 | 250 | 500)