Lately I had to reconfigure an Ubuntu 14.04 server.
Dealing with Tomcat 7 I’ve encountered those two situations:
Enable larger file uploads via Tomcat manager
I had a ~180 war file to deploy. Ubuntu’s Tomcat setting put a limit at 50MB. This has been solved using the tips in this post by skotfred. Unfortunately I haven’t found a more orthodox way of achieving this other than modify the /usr/share/tomcat7-admin/manager/WEB-INF/web.xml in the values max-file-size and max-request-size.
Enable Tomcat monitoring in Munin
Here I’ve followed the tips over this Serverfault discussions.
Adding a [tomcat_ *] was the key.
During the previous week I found myself trying to manage an early 2008 iMac with some serious issues booting. After having tried any trick I knew I decided myself to use the Apple’s Hardware Tests. Here I found some glitches with the fans. This mac was used in a man’s luxury tailor shop … so the outside was shiny!
Never I could ever imagine the amount of dust collected inside…
Without opening the iMac chassis I tried a first cleaning using an air-compressor. Then I remembered of smcFanControl, a software more commonly used to tame the heating of Apple’s notebooks. After the download I’ve started it and created a new cooling profile called “Cleaning” setting all the 3 fans inside the iMac to their maximum speed. Then I’ve selected it and … WOW … a cloud of dust was blown away from all the case’s fences! Incredible!
I had the iMac running this way for near twenty minutes, then made come it back to its default. Since then the iMac is working smoothly like when it was brand new. Zero euro spent, maximum result!
At work we’re in the middle of the development of a new Tomcat powered bioinformatics application, and have reached the stage were you have to show it to some peers but not make it publicly available. I do have an ubuntu 12.04 LTS server, so I took the most out of this Randeep’s post:
Here it is how to do it in few steps:
- Add user, password and role in conf/tomcat-users.xml
- In the webapps/examples/WEB-INF/web.xml specify role, method and urls.
- Restart Tomcat and check the result
The other day, after a do-release-update on an Ubuntu box I had some issues with a package which told me:
Errors were encountered while processing: BROKEN-PACKAGE E: Sub-process /usr/bin/dpkg returned an error code (1)
here’s how I solved:
mv /var/lib/dpkg/info/BROKEN-PACKAGE.* /tmp/ dpkg --remove --force-remove-reinstreq BROKEN-PACKAGE
The accepted rule for backup best practices is the three-two-one rule. It can be summarized as: if you’re backing something up, you should have:
- At least three copies,
- In two different formats,
- with one of those copies off-site.