Maintenance http://hcmc.uvic.ca/blogs/index.php?blog=11 HCMC Maintenance en-CA hourly 1 2000-01-01T12:00+00:00 Tomcat upgrade on peach - problems http://hcmc.uvic.ca/blogs/index.php?blog=11&title=tomcat_upgrade_on_peach_problems&more=1&c=1&tb=1&pb=1 2013-06-11T15:54:41Z Greg Servers (Mins: 45) Last night we upgraded Tomcat on peach to the latest version in order to take advantage of some recent GC optimizations. Unfortunately it also included a security fix that broke all of our Cocoon apps. So, bcgenesis, mariage, ach, myndir, etc. were dead. Sysadmin fixed some of them with an adjustment to the web.xml file inside of each app like this: Around line 708 in <app-name>/WEB-INF/web.xml, look for <servlet-mapping> <servlet-name>WebDAVServlet</servlet-name> <url-pattern>/webdav/*</url-pattern> </servlet-mapping> and change webdav/* to something else, like webdavservlet/* Mins: 45

Last night we upgraded Tomcat on peach to the latest version in order to take advantage of some recent GC optimizations. Unfortunately it also included a security fix that broke all of our Cocoon apps. So, bcgenesis, mariage, ach, myndir, etc. were dead. Sysadmin fixed some of them with an adjustment to the web.xml file inside of each app like this: Around line 708 in <app-name>/WEB-INF/web.xml, look for <servlet-mapping> <servlet-name>WebDAVServlet</servlet-name> <url-pattern>/webdav/*</url-pattern> </servlet-mapping> and change webdav/* to something else, like webdavservlet/* Last night we upgraded Tomcat on peach to the latest version in order to take advantage of some recent GC optimizations. Unfortunately it also included a security fix that broke all of our Cocoon apps. So, bcgenesis, mariage, ach, myndir, etc. were dead.

Sysadmin fixed some of them with an adjustment to the web.xml file inside of each app like this:

Around line 708 in <app-name>/WEB-INF/web.xml, look for
<servlet-mapping>
<servlet-name>WebDAVServlet</servlet-name>
<url-pattern>/webdav/*</url-pattern>
</servlet-mapping>

and change webdav/* to something else, like webdavservlet/*

]]> Changed group settings on Moses EMLS and Scraps blogs http://hcmc.uvic.ca/blogs/index.php?blog=11&title=changed_group_settings_on_moses_emls_and&more=1&c=1&tb=1&pb=1 2013-05-29T17:48:30Z sarneil Activity log (Mins: 30) I have a bunch of new users to add to the system and make members of the CanMys blog. When I added the first and logged in as him, I noticed that when I clicked on the Posts button, I was allowed to see posts from the Moses, EMCS and Scraps blogs. Turns out those three blogs had group permissions which made all users of type "Blogger" members and with permission to upload to the media folder, but do nothing else. Those three blogs also have individual users with specific permissions. I disabled the is-member checkbox for Bloggers in the group permissions for each of those three blogs. That automatically disabled the upload checkbox. There should be no change of behaviour for specific users that are members of those blogs. Mins: 30

I have a bunch of new users to add to the system and make members of the CanMys blog. When I added the first and logged in as him, I noticed that when I clicked on the Posts button, I was allowed to see posts from the Moses, EMCS and Scraps blogs. Turns out those three blogs had group permissions which made all users of type "Blogger" members and with permission to upload to the media folder, but do nothing else. Those three blogs also have individual users with specific permissions. I disabled the is-member checkbox for Bloggers in the group permissions for each of those three blogs. That automatically disabled the upload checkbox. There should be no change of behaviour for specific users that are members of those blogs. I have a bunch of new users to add to the system and make members of the CanMys blog. When I added the first and logged in as him, I noticed that when I clicked on the Posts button, I was allowed to see posts from the Moses, EMCS and Scraps blogs. Turns out those three blogs had group permissions which made all users of type "Blogger" members and with permission to upload to the media folder, but do nothing else. Those three blogs also have individual users with specific permissions.
I disabled the is-member checkbox for Bloggers in the group permissions for each of those three blogs. That automatically disabled the upload checkbox. There should be no change of behaviour for specific users that are members of those blogs.

]]> javaws not running jnlp files http://hcmc.uvic.ca/blogs/index.php?blog=11&title=javaws_not_running_jnlp_files&more=1&c=1&tb=1&pb=1 2013-05-27T19:34:18Z Greg Documentation (Mins: 0) To fix this problem, run sudo update-alternatives --config javaws and choose the java 7 version Mins: 0

To fix this problem, run sudo update-alternatives --config javaws and choose the java 7 version To fix this problem, run
sudo update-alternatives --config javaws
and choose the java 7 version

]]> Java headless http://hcmc.uvic.ca/blogs/index.php?blog=11&title=java_headless&more=1&c=1&tb=1&pb=1 2013-05-17T16:20:57Z Greg Servers (Mins: 15) The ISE was getting the error java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment when running xwiki. It turns out that the existence of quotes in JAVA_OPTS directives causes the option to be ignored. So, for future reference, use -Djava.awt.headless=true instead of -Djava.awt.headless="true" when launching tomcat on a headless server. Mins: 15

The ISE was getting the error java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment when running xwiki. It turns out that the existence of quotes in JAVA_OPTS directives causes the option to be ignored. So, for future reference, use -Djava.awt.headless=true instead of -Djava.awt.headless="true" when launching tomcat on a headless server. The ISE was getting the error
java.lang.NoClassDefFoundError: Could not initialize class sun.awt.X11GraphicsEnvironment
when running xwiki.
It turns out that the existence of quotes in JAVA_OPTS directives causes the option to be ignored. So, for future reference, use -Djava.awt.headless=true instead of -Djava.awt.headless="true" when launching tomcat on a headless server.

]]> Rsync problem on rutabaga http://hcmc.uvic.ca/blogs/index.php?blog=11&title=rsync_problem_on_rutabaga&more=1&c=1&tb=1&pb=1 2013-05-09T17:14:12Z Greg Servers (Mins: 120) After an update to DSM 4.2 rutabaga no longer allowed rsync backups, failing with: sh: rsync: not found rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: remote command not found (code 127) at io.c(605) [Receiver=3.0.9] After much wailing and gnashing of teeth we discovered that non-interactive users do not have /usr/syno/bin in their path (it *is* in their path if they shell in to the NAS, so they can run rsync *from* the NAS when shell'd in). So, that's an easy fix, says us: add a symlink to /usr/syno/bin/rsync in a logical spot that *is* in a non-interactive path, like /usr/bin. Problem: admin user cannot su root (error message = su: must be suid to work properly), so cannot create symlink. Answer: TURN ON TELNET AND LOG IN AS ROOT USING THE WORST POSSIBLE METHOD!!! Then, you make the symlink and turn off telnet - quick! Mins: 120

After an update to DSM 4.2 rutabaga no longer allowed rsync backups, failing with: sh: rsync: not found rsync: connection unexpectedly closed (0 bytes received so far) [Receiver] rsync error: remote command not found (code 127) at io.c(605) [Receiver=3.0.9] After much wailing and gnashing of teeth we discovered that non-interactive users do not have /usr/syno/bin in their path (it *is* in their path if they shell in to the NAS, so they can run rsync *from* the NAS when shell'd in). So, that's an easy fix, says us: add a symlink to /usr/syno/bin/rsync in a logical spot that *is* in a non-interactive path, like /usr/bin. Problem: admin user cannot su root (error message = su: must be suid to work properly), so cannot create symlink. Answer: TURN ON TELNET AND LOG IN AS ROOT USING THE WORST POSSIBLE METHOD!!! Then, you make the symlink and turn off telnet - quick! After an update to DSM 4.2 rutabaga no longer allowed rsync backups, failing with:

sh: rsync: not found
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: remote command not found (code 127) at io.c(605) [Receiver=3.0.9]

After much wailing and gnashing of teeth we discovered that non-interactive users do not have /usr/syno/bin in their path (it *is* in their path if they shell in to the NAS, so they can run rsync *from* the NAS when shell'd in).

So, that's an easy fix, says us: add a symlink to /usr/syno/bin/rsync in a logical spot that *is* in a non-interactive path, like /usr/bin.

Problem: admin user cannot su root (error message = su: must be suid to work properly), so cannot create symlink.

Answer: TURN ON TELNET AND LOG IN AS ROOT USING THE WORST POSSIBLE METHOD!!! Then, you make the symlink and turn off telnet - quick!

]]> Network troubles - solved http://hcmc.uvic.ca/blogs/index.php?blog=11&title=network_troubles_solved&more=1&c=1&tb=1&pb=1 2013-05-08T21:57:09Z Greg Activity log (Mins: 120) This morning we got nets to set up B047 on the switch. Some time after that 3 machines lost the ability to get a DHCP address - I have no idea if there is a causal relationship between these things. After much mucking about, it *looks* like it might have been a communication problem between the DHCP server and the machines. Even forcibly releasing the DHCP lease didn't make any difference. In the end, I booted the machine with a LiveCD and fiddled with enabling/disabling the network (in the network manger). I got a proper IP and rebooted in the installed OS. That seemed to break it out of the loop. A bit perplexing and aggravating because I don't actually know what the problem was... Mins: 120

This morning we got nets to set up B047 on the switch. Some time after that 3 machines lost the ability to get a DHCP address - I have no idea if there is a causal relationship between these things. After much mucking about, it *looks* like it might have been a communication problem between the DHCP server and the machines. Even forcibly releasing the DHCP lease didn't make any difference. In the end, I booted the machine with a LiveCD and fiddled with enabling/disabling the network (in the network manger). I got a proper IP and rebooted in the installed OS. That seemed to break it out of the loop. A bit perplexing and aggravating because I don't actually know what the problem was... This morning we got nets to set up B047 on the switch. Some time after that 3 machines lost the ability to get a DHCP address - I have no idea if there is a causal relationship between these things.

After much mucking about, it *looks* like it might have been a communication problem between the DHCP server and the machines.
Even forcibly releasing the DHCP lease didn't make any difference.

In the end, I booted the machine with a LiveCD and fiddled with enabling/disabling the network (in the network manger). I got a proper IP and rebooted in the installed OS. That seemed to break it out of the loop.

A bit perplexing and aggravating because I don't actually know what the problem was...

]]> All projects moved to Peach http://hcmc.uvic.ca/blogs/index.php?blog=11&title=all_projects_moved_to_peach&more=1&c=1&tb=1&pb=1 2013-03-26T20:26:53Z mholmes R & D (Mins: 180) All current Tomcat-based projects have now been moved to Peach, with the help of RE, who has re-pointed all the relevant domains. The IALLTJournal project has been retired, since it's no longer in use, as has the old version of Francotoile, which was built on eXist 1.4. This was a fairly slow and careful migration over a couple of days, and we expect no problems, but Pear will continue to run for a little while just in case. Mins: 180

All current Tomcat-based projects have now been moved to Peach, with the help of RE, who has re-pointed all the relevant domains. The IALLTJournal project has been retired, since it's no longer in use, as has the old version of Francotoile, which was built on eXist 1.4. This was a fairly slow and careful migration over a couple of days, and we expect no problems, but Pear will continue to run for a little while just in case. All current Tomcat-based projects have now been moved to Peach, with the help of RE, who has re-pointed all the relevant domains. The IALLTJournal project has been retired, since it's no longer in use, as has the old version of Francotoile, which was built on eXist 1.4. This was a fairly slow and careful migration over a couple of days, and we expect no problems, but Pear will continue to run for a little while just in case.

]]> Testing on Peach http://hcmc.uvic.ca/blogs/index.php?blog=11&title=testing_on_peach&more=1&c=1&tb=1&pb=1 2013-02-01T19:29:36Z mholmes R & D (Mins: 30) Tomcat has now been configured so that a slash not followed by a filename is handled by the webapp, not trapped as an error by Tomcat itself. I've also uploaded and tested the new Moses app on Peach, confirming that while the eXist dashboard and eXide fail under Tomcat 6, they work under Tomcat 7. Mins: 30

Tomcat has now been configured so that a slash not followed by a filename is handled by the webapp, not trapped as an error by Tomcat itself. I've also uploaded and tested the new Moses app on Peach, confirming that while the eXist dashboard and eXide fail under Tomcat 6, they work under Tomcat 7. Tomcat has now been configured so that a slash not followed by a filename is handled by the webapp, not trapped as an error by Tomcat itself. I've also uploaded and tested the new Moses app on Peach, confirming that while the eXist dashboard and eXide fail under Tomcat 6, they work under Tomcat 7.

]]> Creating a gource visualization of SVN work http://hcmc.uvic.ca/blogs/index.php?blog=11&title=creating_a_gource_visualization_of_svn_w&more=1&c=1&tb=1&pb=1 2013-01-23T21:58:53Z mholmes Activity log (Mins: 30) To create a visualization with gource (on Linux), first install gource (it's in the Ubuntu repo), then: cd [the SVN directory you want to work on] svn log -r 11019:11452 --xml --verbose --quiet > svnlog.xml [Choose the revision numbers you want.] gource -1280x720 -o - svnlog.xml | ffmpeg -y -r 60 -f image2pipe -vcodec ppm -i - -vcodec libx264 -preset ultrafast -crf 1 -threads 0 -bf 0 video.mp4 Mins: 30

To create a visualization with gource (on Linux), first install gource (it's in the Ubuntu repo), then: cd [the SVN directory you want to work on] svn log -r 11019:11452 --xml --verbose --quiet > svnlog.xml [Choose the revision numbers you want.] gource -1280x720 -o - svnlog.xml | ffmpeg -y -r 60 -f image2pipe -vcodec ppm -i - -vcodec libx264 -preset ultrafast -crf 1 -threads 0 -bf 0 video.mp4 To create a visualization with gource (on Linux), first install gource (it's in the Ubuntu repo), then:

cd [the SVN directory you want to work on]

svn log -r 11019:11452 --xml --verbose --quiet > svnlog.xml
[Choose the revision numbers you want.]

gource -1280x720 -o - svnlog.xml | ffmpeg -y -r 60 -f image2pipe -vcodec ppm -i - -vcodec libx264 -preset ultrafast -crf 1 -threads 0 -bf 0 video.mp4
]]> ssh recursively remove folders and their contents http://hcmc.uvic.ca/blogs/index.php?blog=11&title=ssh_recursively_remove_folders_and_their&more=1&c=1&tb=1&pb=1 2013-01-16T18:33:13Z sarneil Documentation (Mins: 0) to recursively remove folders and their contents rm -rf path/to/folder Mins: 0

to recursively remove folders and their contents rm -rf path/to/folder