Ran into a couple of problems here:
Default Debian behaviour is to mount cd’s with noexec option. Thus you get permission denied even as root when you try to run the install script. Solution; remount cd:
sudo mount -o remount,exec,ro /media/cdrom0
or whatever path the cd is mounted at. You need the ro otherwise it complains.
Other more general problem: sudo ./install just results in Installing... Finished and a silent fail. In the old days using gksudo fixed this but apparently it’s deprecated now. It does work when running as normal user, so tried:
Read more...
First user in Ubuntu 14.04.3 has membership of groups:
- adm
- cdrom
- sudo
- dip
- plugdev
- lpadmin
- sambashare
Another user created as administrator from the GUI gets:
- adm
- sudo
- lpadmin
- sambashare
We had a problem with a couple of users who kept having synchronisation problems with an Exchange (2010) server, using Outlook 2010. Some mail would not appear in mailboxes, but would appear in the web client. The sync would claim to complete ok, but looking at the Sync Issues folder there were a lot of messages of the form:
13:22:28 Error Synchronizing Hierarchy for Mailbox 'TeamShared'
13:22:28 [80040305-54A-4DE-1900]
13:22:28 Your server administrator has limited the number of items you can open simultaneously. Try closing messages you have opened or removing attachments and images from unsent messages you are composing.
This can occur if the secondary mailbox has a a lot of folders, which this one does – there’s a big tree of stuff in there. To solve this we turned off caching of the secondary mailbox. The details of the problem and the various workarounds are given at:
Read more...
See https://weakdh.org for the problem – 1024 bit Diffie-Hellman keys are potentially breakable (the ‘logjam’ vulnerability). This can be fixed in Apache 2.4 by pointing it at a custom key, but up to recently ver 2.2 was vulnerable. The issue was fixed in apache 2.2.22-13+deb7u5, which allows a custom DH key to be appended to the server certificate. To use this in Debian 7:
Update to apache 2.2.22-13+deb7u5 or higher.
Generate a new Diffie-Hellman group using
Read more...
After much problems with getting a new Proxmox cluster up and running two things have helped:
Putting the SAN IP addresses in the hosts file, avoiding DNS dependancies (especially when one of the systems isn’t in there yet…). This put me on track: http://blog.rhavenindustrys.com/2013/04/curious-proxmox-clustering-fix.html
Important bit:
127.0.0.1 localhost.localdomain localhost
169.254.0.1 proxmox1.local proxmox1 pvelocalhost
169.254.0.2 proxmox2.local proxmox2
10.10.5.101 proxmox1.example.com
10.10.5.102 proxmox2.example.com
This associates the short aliases with the network used by corosync, while leaving the long addresses to the outside world.
Read more...