Difference between revisions of "Software Issues"
m |
m |
||
| Line 8: | Line 8: | ||
; [[Postfix]] : Mail transfer agent that routes and delivers e-mail | ; [[Postfix]] : Mail transfer agent that routes and delivers e-mail | ||
; [[SpamAssassin]] : Filters out junk mail sent through it by postfix | ; [[SpamAssassin]] : Filters out junk mail sent through it by postfix | ||
| + | |||
| + | = Jalapeno SSH problems = | ||
| + | |||
| + | After the air conditioning install in May 2010, once we'd moved all of the systems back into the server room, we had some issues with connecting to [[Jalapeno]]. The system seemed to be working correctly, but would drop SSH connections shortly after they had been established, and it would often be difficult to establish a connection in the first place. Usually when the SSH connection failed it would return this error: | ||
| + | |||
| + | Write failed: Broken pipe. | ||
| + | |||
| + | There didn't appear to be anything wrong with the system or its SSH configuration. Later we discovered that the backup copy of Jalapeno on [[Taro]] had started automatically when Taro was booted, and the conflict between the two jalapeno systems was causing its network issues. If you have this issue with a virtual system make sure to check that it is the only copy of that VM running on any virtual host. | ||
= User Software = | = User Software = | ||
; [[Firefox]] | ; [[Firefox]] | ||
Revision as of 17:50, 23 June 2010
einstein LDAP crash
Einstein said that service ldap was running, however, nothing could reach the server, not even local ldapsearches. It turns out that the Berkley database was corrupted due to a bad shutdown earlier in the day.
In case this happens again, follow this procedure. There should be physical copies of this in the server room in case the wiki is unavailable
Mail Chain Dependencies
When updating any one of these, it is important to shut down all of them beforehand. More
- Postfix
- Mail transfer agent that routes and delivers e-mail
- SpamAssassin
- Filters out junk mail sent through it by postfix
Jalapeno SSH problems
After the air conditioning install in May 2010, once we'd moved all of the systems back into the server room, we had some issues with connecting to Jalapeno. The system seemed to be working correctly, but would drop SSH connections shortly after they had been established, and it would often be difficult to establish a connection in the first place. Usually when the SSH connection failed it would return this error:
Write failed: Broken pipe.
There didn't appear to be anything wrong with the system or its SSH configuration. Later we discovered that the backup copy of Jalapeno on Taro had started automatically when Taro was booted, and the conflict between the two jalapeno systems was causing its network issues. If you have this issue with a virtual system make sure to check that it is the only copy of that VM running on any virtual host.
