How to , and other stuff about linux, photo, php … A linux, photography blog. To remember some linux situation, and fix them quickly.

September 5, 2013

svn: E170000: Unrecognized URL scheme for http*

Filed under: Linux — admin @ 10:03 am

Hello
Well in the few past day I upgraded some svn to 1.7 . First problem is this. with Unrecognized URL scheme for http.
Well it appear that you need neon for this .
So here we go
wget http://www.webdav.org/neon/neon-0.29.3.tar.gz
tar -xzvf neon-0.29.3.tar.gz
cd neon-0.29.3
./configure --with-ssl
make
make install
Also I think yum install neon-devel should work also . But didn’t try it .

Now if you have a error with sqlite, you have to install sqlite-devel on your server .

After this
wget http://mirrors.hostingromania.ro/apache.org/subversion/subversion-1.7.13.tar.gz
tar -zxvf subversion-1.7.13.tar.gz
cd subversion-1.7.13
./configure --with-ssl --with-neon=/usr/local
make
make install

Now this is for centos, if you have debian you should install more programs. I did try to upgrade a debian and took me some time to do this .

Regards

September 2, 2013

ispconfig dovecot: auth: Error: Can’t open configuration file /etc/dovecot-sql.conf

Filed under: Linux — admin @ 10:17 am

Well today I am trying to setup a ispconfig. When I try to log on mail I have a wired problem that imap is not working. So when I looked into maillog I see this error
auth: Error: Can’t open configuration file /etc/dovecot-sql.conf

Well the fis is pretty simple .
ln -s /etc/dovecot/dovecot-sql.conf /etc/dovecot-sql.conf
ln -s /etc/dovecot/dovecot.conf /etc/dovecot.conf

After this restart dovecot, and the mail will work.

July 24, 2013

Setting up tunnel in WinSCP

Filed under: Linux — admin @ 11:10 am

Hello
I know that this post is like copy paste however I wanted for me to be here. Mainly I use this site so not to search again some information . I came here and use it. Today I wanted to copy some files from server B, that I can access it only from server A. But I am on host C. So how to do it ?
Well start cmd where is your putty located and run there
putty.exe -L 3111::22

Where 3111 will be forwarded port port 22 on server B
Now on my computer C I open winscp and connect to localhost and port 3111.

That’s all .

May 9, 2013

Virtualbox same UUID as an existing virtual machine

Filed under: Linux — Tags: , — admin @ 11:49 am

Long time no post.
Well because I want to test a lot of things, well I work with virtual box. Well but because I need more then one server on my virtual network I have to use same image more time to create more instances. However if you want to add another instance with same vdi/vbox file you will have the error.
“Trying to open virtual machine located in … vbox
“Trying to open a VM config ‘…vbox’ witch has the same UUID as an existing virtual machine.”

Well unfortunately there is no short fix with some dialog box to hit it. So to fix this you have to go on folder where is your virtbualbox installed if is not in default directory as

C:\Program Files\Oracle\VirtualBox\

And run this
VBoxManage.exe internalcommands sethduuid “c:\path\MyVM.vdi”

Now you can hit new button chose what you want and on third section just pick up “use an existing virtual hard drive file” and pick this c:\path\MyVM.vdi

Hope will help someone.

March 14, 2013

Varnish Error 503 Service unavailable… Guru Meditation

Filed under: Linux — Tags: , , — admin @ 2:07 pm

Today I have face a big problem while using varnish with nginxcp + cpanel on a vps server .
Well the main site was working that was using a wordpress, however admin area because have a lot of plugins crashed with that stupid error.
So after a long search in ngnix log I find this error
upstream prematurely closed connection while reading response header from upstream
and this
an upstream response is buffered to a temporary file

However this seem’s that are not the problem for unavailable problem. However a fix for those error is to disable log in proxy.inc just add
proxy_buffering off;

However the fix is this in the varnish configuration default.vcl
backend default {
.host = “127.0.0.1”;
.port = “81”;
}

So after I modify this with

backend default {
.host = “127.0.0.1”;
.port = “81”;
.connect_timeout = 120s;
.first_byte_timeout = 120s;
.between_bytes_timeout = 120s;
}

The problem suddenly disappear . So basically the timeout should be increased for admin area if you have a lot of plugins there in wordpress and you are on a small vps.

« Newer Posts — Older Posts »

Powered by WordPress