I can see my repository in a web browser, but ’svn checkout’ gives me an error about “301 Moved Permanently”. What’s wrong?
It means your httpd.conf is misconfigured. Usually this error happens when you’ve defined the Subversion virtual “location” to exist within two different scopes at the same time.
For example, if you’ve exported a repository as , but you’ve also set your DocumentRoot to be /www, then you’re in trouble. When the request comes in for /www/foo/bar, apache doesn’t know whether to find a real file named /foo/bar within your DocumentRoot, or whether to ask mod_dav_svn to fetch a file /bar from the /www/foo repository. Usually the former case wins, and hence the “Moved Permanently” error.
The solution is to make sure your repository does not overlap or live within any areas already exported as normal web shares.
It’s also possible that you have an object in the web root which has the same name as your repository URL. For example, imagine your web server’s document root is /var/www and your Subversion repository is located at /home/svn/repo. You then configure Apache to serve the repository at http://localhost/myrepo. If you then create the directory /var/www/myrepo/ this will cause a 301 error to occur.
Popularity: 2% [?]
Tags: subversion
Source: http://ubuntuforums.org/showthread.php?t=791804
setup
1. sudo apt-get install apache2
2. sudo apt-get install openssl
3. sudo apt-get install ssl-cert
create ssl certificate:
sudo make-ssl-cert /usr/share/ssl-cert/ssleay.cnf /etc/ssl/private/localhost.pem
switch to apache sites configuration:
cd /etc/apache2/sites-available/
bakup the default configuration:
sudo cp default default.backup.date
be sure to listen the port 80 for the default:
sudo sed -i ‘1,2s/\*/*:80/’ default
create the ssl configuration:
sudo cp default ssl
set the ssl port:
sudo sed -i ‘1,2s/\*:80/*:443/’ ssl
sudo sed -i “3a\\\tSSLEngine On\n\tSSLCertificateFile /etc/ssl/private/localhost.pem” ssl
enable ssl:
sudo a2ensite ssl
sudo a2enmod ssl
restart apache2:
sudo /etc/init.d/apache2 restart
Popularity: 19% [?]
1. You have to install qemu. http://free.oszoo.org/ftp/qemu/win32/release/QemuInstall-0.7.2.exe 2. cd c:\Program files\qemu qemu-img.exe convert -O vmdk hdd.vdi hdd.vmdk
Popularity: 73% [?]
Tags: VirtualBox
Most wanted question:
1. How do I access PostgreSQL through the network?
1.1. Open postgresql.conf (in Ubuntu 8.04 at /etc/postgresql/8.3/main/postgresql.conf) and change listen_addresses = ‘localhost’ to listen_addresses = ‘*’.
1.2. Uncomment password_encryption = on.
1.3. Open /etc/postgresql/8.3/main/pg_hba.conf
host all all / trust
eg. host all all 192.168.2.0/24 trust
1.4. Restart PostgreSQL
/etc/init.d/postgresql-8.3
Yes! That works fine!
Popularity: 1% [?]
Tags: postgresql
From linux command prompt:
su - postgres
psql -d template1 -U postgres
alter user postgres with password 'postgres_password';
ctrl+d
Popularity: 1% [?]
Tags: postgresql
Oops.
All it needed was
/etc/nagios2#/etc/init.d/nagios2 stop
Stopping nagios2 monitoring daemon: nagios2.
/etc/nagios2# dpkg-statoverride –update –add nagios www-data 2710 /var/lib/nagios2/rw
/etc/nagios2# dpkg-statoverride –update –add nagios nagios 751 /var/lib/nagios2
/etc/nagios2# /etc/init.d/nagios2 start
Starting nagios2 monitoring daemon: nagios2.
ref. http://ubuntuforums.org/showthread.php?t=458375
Popularity: 1% [?]
Tags: nagios
Table 2. Plugin Return Codes
| Numeric Value | Service Status | Status Description |
|---|---|---|
| 0 | OK | The plugin was able to check the service and it appeared to be functioning properly |
| 1 | Warning | The plugin was able to check the service, but it appeared to be above some “warning” threshold or did not appear to be working properly |
| 2 | Critical | The plugin detected that either the service was not running or it was above some “critical” threshold |
| 3 | Unknown | Invalid command line arguments were supplied to the plugin or low-level failures internal to the plugin (such as unable to fork, or open a tcp socket) that prevent it from performing the specified operation. Higher-level errors (such as name resolution errors, socket timeouts, etc) are outside of the control of plugins and should generally NOT be reported as UNKNOWN states. |
link: http://nagiosplug.sourceforge.net/developer-guidelines.html#AEN35
Popularity: 1% [?]
root@srv:~# mysql -p
Enter password:
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 14 to server version: 5.0.24a-Debian_9ubuntu2.4-log
Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the buffer.
mysql> GRANT ALL ON *.* TO root@’%’ IDENTIFIED BY ‘password_you_want’;
Query OK, 0 rows affected (0.00 sec)
mysql>
Popularity: 1% [?]
Tags: mysql
Today I had an interesting issue on Ubuntu 8.10.
We have 2 NICS on the server one has the following ip 172.16.20.10/16 and another one has 172.16.60.10/16. I know they are on the same network though but we had to do it in order to accomplish some routing issues.
So here is the problem:
When I try to ping our ISPs Gateway it succesful pings till the eighth or ninth reply and stops replying.
On ubuntu 6.10 it works fine.
So here is the solution:
Since we have 2 NICs with the same network address when the second one tries to reach a remote server the Kernel thinks it is a spoofing attack since by default it is enable source address verification against spoofing attacks.
So what you have to do is to change the rp_filter kernel parameter to 0 (zero).
1. Edit 10-network-security.conf
vi /etc/sysctl.d/10-network-security.conf
change to 0 (zero)
2. invoke-rc.d procps start
This is it!
Leonardo
Popularity: 1% [?]
Tags: kernel