itemprop="text"> I have apache2 running on Ubuntu 14.04.2 LTS. The problem is, I keeps getting the following error ( tail -f /var/log/apache2/error.log ) [Wed Jun 10 18:18:56.114203 2015] [core:error] [pid 14802] [client 10.0.0.100:48843] AH00037: Symbolic link not allowed or link target not accessible: /var/www/html/xxxx In file: /etc/apache2/sites-enabled/000-default.conf I have DocumentRoot /var/www/html Options +FollowSymLinks AllowOverride None In /var/www/html directory, I have a softlink called "xxxx" pointing to /root/xxxx I restarted the apache by service apache2 restart But it didn't help. Any ideas? bold;"> Answer Turns out my /root directory didn't have the right permission for www-data ...

I have apache2 running on Ubuntu 14.04.2 LTS. The problem is, I keeps getting the following error ( tail -f /var/log/apache2/error.log ) [Wed Jun 10 18:18:56.114203 2015] [core:error] [pid 14802] [client 10.0.0.100:48843] AH00037: Symbolic link not allowed or link target not accessible: /var/www/html/xxxx In file: /etc/apache2/sites-enabled/000-default.conf I have DocumentRoot /var/www/html Options +FollowSymLinks AllowOverride None In /var/www/html directory, I have a softlink called "xxxx" pointing to /root/xxxx I restarted the apache by service apache2 restart But it didn't help. Any ideas? Answer Turns out my /root directory didn't have the right permission for www-data account. Its permission was "drwx------". I did a command chmod a+rx" /root and it works fine now.

itemprop="text"> Suppose I am setting up a new name server at ns1.example.com, and I have properly created the glue record at my registrar to tell the registry that ns1.example.com should point to my name server's IP address at 77.77.77.77. Is there anything in the configuration of my name server that needs to also publish this IP address in a zone? I.e. publish an NS or A record for itself? If the name server didn't publish its own IP address (aside from in the registry glue record) would clients still be able to query me for other records successfully? class="post-text" itemprop="text"> class="normal">Answer The name server needs to publish its own record for the name. Glue records should only be used to "bootstrap" discovery, and then be discarded in favour of the result r...

Suppose I am setting up a new name server at ns1.example.com, and I have properly created the glue record at my registrar to tell the registry that ns1.example.com should point to my name server's IP address at 77.77.77.77. Is there anything in the configuration of my name server that needs to also publish this IP address in a zone? I.e. publish an NS or A record for itself? If the name server didn't publish its own IP address (aside from in the registry glue record) would clients still be able to query me for other records successfully? Answer The name server needs to publish its own record for the name. Glue records should only be used to "bootstrap" discovery, and then be discarded in favour of the result retrieved from the actual authoritative nameservers. I'm not entirely sure what recursive resolvers will do when they get NXDOMAIN for a record they got glue for, but I'm pretty confident it won't be pretty, nor consistent between imp...

I have been administering a few LAMP servers with 2-5 sites on each of them. These are basically owned by the same user/client so there are no security issues except from attacks through vulnerable deamons or scripts. I am builing my own server and would like to start hosting multiple sites. My first concern is... ISOLATION. How can I avoid that a c99 script could deface all the virtual hosts? Also, should I prevent that c99 to be able to write/read the other sites' directories? (It is easy to "cat" a config.php from another site and then get into the mysql database) My server is a VPS with 512M burstable to 1G. Among the free hosting managers, is there any small one which works for my VPS? (which maybe is compatible with the security approach I would like to have) Currently I am not planning to host over 10 sites but I would not accept that a client/hac...

I have been administering a few LAMP servers with 2-5 sites on each of them. These are basically owned by the same user/client so there are no security issues except from attacks through vulnerable deamons or scripts. I am builing my own server and would like to start hosting multiple sites. My first concern is... ISOLATION. How can I avoid that a c99 script could deface all the virtual hosts? Also, should I prevent that c99 to be able to write/read the other sites' directories? (It is easy to "cat" a config.php from another site and then get into the mysql database) My server is a VPS with 512M burstable to 1G. Among the free hosting managers, is there any small one which works for my VPS? (which maybe is compatible with the security approach I would like to have) Currently I am not planning to host over 10 sites but I would not accept that a client/hacker could navigate into unwanted directories or, worse, run malicious scripts. FTP management would be fine. I don't...

I have a new workstation with an unusual high load average. The machine specs are: Xeon CPUs 256 GB of RAM 4 x 512 GB SSD connected to a LSI2108 RAID controller (in raid 5) I have installed CentOS 6.5 64 bit from the live cd, configured the partitions (using LVM), the network, the users/groups, and installed some software like development tools and MATLAB. The workstation load average, after few minutes from the boot, has a value ranging from 0.5 to 0.9. But it is not doing anything. Thus I cannot understand why the load average is so high. Could you help me to diagnose this issue? Here are some information: uname -a Linux delta.grid 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux top top - 15:44:53 up 22 min, 1 user, load average: 0.84, 0.69, 0...

I have a new workstation with an unusual high load average. The machine specs are: Xeon CPUs 256 GB of RAM 4 x 512 GB SSD connected to a LSI2108 RAID controller (in raid 5) I have installed CentOS 6.5 64 bit from the live cd, configured the partitions (using LVM), the network, the users/groups, and installed some software like development tools and MATLAB. The workstation load average, after few minutes from the boot, has a value ranging from 0.5 to 0.9. But it is not doing anything. Thus I cannot understand why the load average is so high. Could you help me to diagnose this issue? Here are some information: uname -a Linux delta.grid 2.6.32-431.el6.x86_64 #1 SMP Fri Nov 22 03:15:09 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux top top - 15:44:53 up 22 min, 1 user, load average: 0.84, 0.69, 0.39 Tasks: 729 total, 1 running, 728 sleeping, 0 stopped, 0 zombie Cpu(s): 0.0%us, 0.0%sy, 0.0%ni,100.0%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 264422908k total, 1986152k used, 262436756k...

I am trying to setup a gitlab instance along an own cloud instance on the same server. Both work fine over http, and both work fine over https if one one host is enabled. The weird thing is that the owncloud host catches all requests to the server, even though the site config only says it should catch one ones to the appropriate domain, and thus prevents the gitlab vhost from answering. Owncloud conf: upstream php-handler { # server 127.0.0.1:9000; server unix:/var/run/php5-fpm.sock; } server { listen 80; server_name cloud.example.com; return 301 https://$server_name$request_uri; # enforce https } server { listen 443 ssl; server_name cloud.example.com; ssl_certificate /etc/ssl/certs/ssl-cert-snakeoil.pem; ssl_certificate_key /etc/ssl/private/ssl-cert-snakeoil.key; # Don't show version...

I am trying to setup a gitlab instance along an own cloud instance on the same server. Both work fine over http, and both work fine over https if one one host is enabled. The weird thing is that the owncloud host catches all requests to the server, even though the site config only says it should catch one ones to the appropriate domain, and thus prevents the gitlab vhost from answering. Owncloud conf: upstream php-handler { # server 127.0.0.1:9000; server unix:/var/run/php5-fpm.sock; } server { listen 80; server_name cloud.example.com; return 301 https://$server_name$request_uri; # enforce https } server { listen 443 ssl; server_name cloud.example.com; ssl_certificate /etc/ssl/certs/ssl-cert-snakeoil.pem; ssl_certificate_key /etc/ssl/private/ssl-cert-snakeoil.key; # Don't show version server_tokens off; # Have separate logs for this vhost ...