bind log
Hi! My syslog is full these errors: Mar 24 09:15:32 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 88.151.100.170#53 Mar 24 09:15:32 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 188.138.15.99#53 Mar 24 09:15:33 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 209.239.123.120#53 Mar 24 09:15:33 tuban named[1541]: error (network unreachable) resolving 'server.lyonessaukcio.hu/A/IN': 2a01:270:2013::9001#53 Mar 24 09:15:33 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 188.138.15.99#53 Mar 24 09:15:33 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 88.151.100.170#53 Mar 24 09:15:33 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 209.239.123.120#53 Mar 24 09:15:33 tuban named[1541]: error (network unreachable) resolving 'server.lyonessaukcio.hu/A/IN': 2a01:270:2013::9001#53 Mar 24 09:15:34 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 188.138.15.99#53 Mar 24 09:15:34 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 88.151.100.170#53 Mar 24 09:15:34 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 209.239.123.120#53 Mar 24 09:15:34 tuban named[1541]: error (network unreachable) resolving 'server.lyonessaukcio.hu/A/IN': 2a01:270:2013::9001#53 Mar 24 09:15:35 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 88.151.100.170#53 Mar 24 09:15:35 tuban named[1541]: error (unexpected RCODE REFUSED) resolving 'server.lyonessaukcio.hu/A/IN': 188.138.15.99#53 how can i prevent BIND doing this? regards: Vuki Debian 6.0.1 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d8afe0c.5070...@informatik.hu
dovecot sieve
Hi All! I have got some problem with dovecot sieve. (from Squeeze packages). I have already intalled dovecot and postfix with mysql(postfix admin) virtual domains and users, configured dovecot deliver for delivery method in postfix. Dovecot sieve IS working, reads the global script, BUT it DOES NOT reads the user scripts from the users virtual home directory. If i place dovecot.sieve in /home/vmail, and configure sieve for this location, it reads the script. If i put the file under /home/vmail/domain.com (/home/vmail/%d) or /home/vmail/domain.com/u...@domain.com (/home/vmail/%d/%u) the sieve plugin does not read the script. Deliver log contains that the incoming mail (which has to be filtered) saved to INBOX, and there is no error in the deliver error log, nor dovecot logs. Can anybosy help me out what am i doing wrong? Vuki dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf . . . mail_location: maildir:/home/vmail/%d/%u mbox_write_locks: fcntl dotlock mail_executable(default): /usr/lib/dovecot/imap mail_executable(imap): /usr/lib/dovecot/imap mail_executable(pop3): /usr/lib/dovecot/pop3 mail_plugin_dir(default): /usr/lib/dovecot/modules/imap mail_plugin_dir(imap): /usr/lib/dovecot/modules/imap mail_plugin_dir(pop3): /usr/lib/dovecot/modules/pop3 lda: postmaster_address: postmas...@informatik.hu hostname: mail.informatik.hu mail_plugins: sieve mail_plugin_dir: /usr/lib/dovecot/modules/lda auth_socket_path: /var/run/dovecot/auth-master log_path: /var/log/dovecot-deliver-errors.log info_log_path: /var/log/dovecot-deliver.log sieve: /home/vmail/%d/dovecot.sieve sieve_dir: /home/vmail/%d/%u/sieve sieve_global_path: /var/lib/dovecot/sieve/default.sieve sieve_global_dir: /var/lib/dovecot/sieve/global/ auth default: user: nobody verbose: yes debug: yes passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: prefetch socket: type: listen client: path: /var/run/dovecot/auth-client mode: 432 user: postfix group: mail master: path: /var/run/dovecot/auth-master mode: 384 user: vmail group: vmail
squeeze volatile
Hi! I do not see squeeze in debian volatile archive. Should not be there? Vuki -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d54dd95.4070...@informatik.hu
lighttpd redirect
Hi Folks! I have a secure site secure.domain.com. It is configured in lighhtpd.conf. I would like to redirect all HTTPS requests to secure.domain.com. So if someone would type, for example, https://www.domain.com, it should be redirected to https://secure.domain.com. Can sy help me to write the redirect rule? vuki -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d4aff02.70...@informatik.hu
logrotate
Hi All!
I have got a strange problem, every day, a got the following error:
/etc/cron.daily/logrotate:
error: apache2_template:1 lines must begin with a keyword or a filename (possibly in double quotes)
error: apache2_template:13 unexpected }
error: found error in file apache2_template, skipping
I checked /etc/logrotate.conf and did not find any problem:
# see "man logrotate" for details
# rotate log files weekly
weekly
# keep 4 weeks worth of backlogs
rotate 4
# create new (empty) log files after rotating old ones
create
# uncomment this if you want your log files compressed
#compress
# packages drop log rotation information into this directory
include /etc/logrotate.d
# no packages own wtmp, or btmp -- we'll rotate them here
/var/log/wtmp {
missingok
monthly
create 0664 root utmp
rotate 1
}
/var/log/btmp {
missingok
monthly
create 0664 root utmp
rotate 1
}
and i also checked /etc/logrotate.d/apache2, but also did not find
anything:
"/var/log/apache2/*.log" {
weekly
missingok
rotate 52
compress
delaycompress
notifempty
create 640 root adm
sharedscripts
postrotate
if [ -f /var/run/apache2.pid ]; then
/etc/init.d/apache2 restart /dev/null
fi
endscript
}
It is an old ETCH box. I do not remember if i ever changed these
config files.
Any suggestions? (Maybe, I am blind?)
vuki
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d45715f.8090...@informatik.hu
stange error
Hi! I am getting the following line in my /var/log/messages, but no any other: Jan 23 06:25:23 algol rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=1500 x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'. What does it mean? Vuki -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d3bef06.1030...@informatik.hu
Re: stange error
Sorry: my system is squeeze amd64 On 2011.01.23. 10:04, Informatik.hu wrote: Hi! I am getting the following line in my /var/log/messages, but no any other: Jan 23 06:25:23 algol rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=1500 x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'. What does it mean? Vuki -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d3bf04c.3020...@informatik.hu
Re: stange error
I have read the thread, BUT. It says to change the ownership of log files to syslog, and set the $FileOwner variable to syslog in /etc/rsyslogd.conf. I do not have syslog user in my system. Shall i create one for this purpose? This bug is ratger old (2009. septembe), has not been fixed yet? On 2011.01.23. 10:22, Mihira Fernando wrote: On 01/23/2011 02:39 PM, Informatik.hu wrote: Sorry: my system is squeeze amd64 On 2011.01.23. 10:04, Informatik.hu wrote: Hi! I am getting the following line in my /var/log/messages, but no any other: Jan 23 06:25:23 algol rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=1500 x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'. What does it mean? Vuki https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/407862 the same problem is discussed in some detail there. Appears the problem is related to rsyslogd log file's permissions. Maybe you're having the same problem ? Mihira. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d3bffde.9080...@informatik.hu
Re: stange error
Hi! Yes, there is some new events in my syslog, so it means this message is by design? My old ETCH box, does not getting this message, thats why i asked You. (also using logrotate, logcheck, logwatch) On 2011.01.23. 13:13, Camaleón wrote: On Sun, 23 Jan 2011 10:04:06 +0100, Informatik.hu wrote: I am getting the following line in my /var/log/messages, but no any other: Jan 23 06:25:23 algol rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=1500 x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'. What does it mean? I read it as rsyslog daemon received a hup signal in the mode lightweight (kinda soft-restart, maybe it was re-engaded on demand by a script in logrotate :-?) Are you getting new entries in the rest of the logs (/var/log/syslog, etc...). messages log file is not very verbose in Debian. Greetings, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d3c1f54.50...@informatik.hu
Re: stange error
On 2011.01.23. 13:49, Camaleón wrote: On Sun, 23 Jan 2011 13:30:12 +0100, Informatik.hu wrote: On 2011.01.23. 13:13, Camaleón wrote: I read it as rsyslog daemon received a hup signal in the mode lightweight (kinda soft-restart, maybe it was re-engaded on demand by a script in logrotate :-?) Are you getting new entries in the rest of the logs (/var/log/syslog, etc...). messages log file is not very verbose in Debian. Yes, there is some new events in my syslog, so it means this message is by design? My old ETCH box, does not getting this message, thats why i asked You. (also using logrotate, logcheck, logwatch) Let me check it in my squeeze... root@debian:~# cat /var/log/messages* | grep lightweight Jan 23 13:12:31 debian rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=869 x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'. Jan 18 12:04:20 debian rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=874 x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'. Jan 19 20:59:28 debian rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=865 x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'. Jan 22 13:05:52 debian rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=872 x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'. Jan 23 13:12:30 debian rsyslogd: [origin software=rsyslogd swVersion=4.6.4 x-pid=869 x-info=http://www.rsyslog.com;] rsyslogd was HUPed, type 'lightweight'. Yes, it seems that message is normal :-) Just ensure your rotated messages (messages.1, messages.2.gz, etc...) contain additional data. Greetings, I have aready checked, every log.n cotains one message, so it is logrotate! :) thx! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d3c2526.8090...@informatik.hu
Re: putting /tmp to memory help
hey, i am also intertested... :) On 2011.01.23. 14:47, kellyremo wrote: to memory means: mounting a ~2 GByte filesystem [ tmpfs?, or ramfs? ], and put the /tmp on it. [ e.g.: 4 GByte ram in the pc ]. what to write in the /etc/fstab? I would like to collect the [ answers too:P ]: Advantages: - Memory is way faster then HDD/SSD, so it could speed things up - SSD amortization is less Disadvantages: - Security? [ how to set this up to be secure? any clear howtos/links regarding it? :O ] Really thank you for any good help... \
squeeze ssd
Hi!
I have got a server with two adata ssds. The server, usually after a
day, drops one of the drives. Are there any configuration parameter,
that i have to set up for ssds?
heres is the log:
Jan 19 15:38:08 algol kernel: [106018.137723] ata1.00: exception Emask
0x0 SAct 0x0 SErr 0x0 action 0x6 frozen
Jan 19 15:38:08 algol kernel: [106018.137808] ata1.00: failed command:
FLUSH CACHE
Jan 19 15:38:08 algol kernel: [106018.137857] ata1.00: cmd
e7/00:00:00:00:00/00:00:00:00:00/a0 tag 0
Jan 19 15:38:08 algol kernel: [106018.137858] res
40/00:00:00:00:00/00:00:00:00:00/10 Emask 0x4 (timeout)
Jan 19 15:38:08 algol kernel: [106018.137988] ata1.00: status: { DRDY }
Jan 19 15:38:08 algol kernel: [106018.138037] ata1.00: hard resetting link
Jan 19 15:38:09 algol kernel: [106018.457245] ata1.01: hard resetting link
Jan 19 15:38:09 algol kernel: [106018.932576] ata1.00: SATA link down
(SStatus 0 SControl 300)
Jan 19 15:38:09 algol kernel: [106018.932591] ata1.01: SATA link up 3.0
Gbps (SStatus 123 SControl 300)
Jan 19 15:38:14 algol kernel: [106023.925113] ata1.00: hard resetting link
Jan 19 15:38:14 algol kernel: [106024.244632] ata1.01: hard resetting link
Jan 19 15:38:15 algol kernel: [106024.719961] ata1.00: SATA link down
(SStatus 0 SControl 300)
Jan 19 15:38:15 algol kernel: [106024.719976] ata1.01: SATA link up 3.0
Gbps (SStatus 123 SControl 300)
Jan 19 15:38:15 algol kernel: [106024.737140] ata1.00: limiting SATA
link speed to 1.5 Gbps
Jan 19 15:38:20 algol kernel: [106029.712472] ata1.00: hard resetting link
Jan 19 15:38:20 algol kernel: [106030.032009] ata1.01: hard resetting link
Jan 19 15:38:21 algol kernel: [106030.507348] ata1.00: SATA link down
(SStatus 0 SControl 310)
Jan 19 15:38:21 algol kernel: [106030.507363] ata1.01: SATA link up 3.0
Gbps (SStatus 123 SControl 300)
Jan 19 15:38:21 algol kernel: [106030.524516] ata1.00: disabled
Jan 19 15:38:21 algol kernel: [106030.532485] ata1.01: configured for
UDMA/133
Jan 19 15:38:21 algol kernel: [106030.532491] ata1.00: device reported
invalid CHS sector 0
Jan 19 15:38:21 algol kernel: [106030.532502] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.532557] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.532607] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.532655] end_request: I/O error,
dev sda, sector 17397664
Jan 19 15:38:21 algol kernel: [106030.532705] raid1: Disk failure on
sda2, disabling device.
Jan 19 15:38:21 algol kernel: [106030.532706] raid1: Operation
continuing on 1 devices.
Jan 19 15:38:21 algol kernel: [106030.532805] ata1: EH complete
Jan 19 15:38:21 algol kernel: [106030.532822] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.532873] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.532923] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.532972] sd 0:0:0:0: [sda] READ
CAPACITY(16) failed
Jan 19 15:38:21 algol kernel: [106030.532973] sd 0:0:0:0: [sda] Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jan 19 15:38:21 algol kernel: [106030.532976] sd 0:0:0:0: [sda] Sense
not available.
Jan 19 15:38:21 algol kernel: [106030.532979] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.533028] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.533078] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.533126] sd 0:0:0:0: [sda] READ
CAPACITY failed
Jan 19 15:38:21 algol kernel: [106030.533127] sd 0:0:0:0: [sda] Result:
hostbyte=DID_NO_CONNECT driverbyte=DRIVER_OK
Jan 19 15:38:21 algol kernel: [106030.533130] sd 0:0:0:0: [sda] Sense
not available.
Jan 19 15:38:21 algol kernel: [106030.533132] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.533182] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.533232] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.533282] sd 0:0:0:0: rejecting I/O
to offline device
Jan 19 15:38:21 algol kernel: [106030.51] sd 0:0:0:0: [sda] Asking
for cache data failed
Jan 19 15:38:21 algol kernel: [106030.533379] sd 0:0:0:0: [sda] Assuming
drive cache: write through
Jan 19 15:38:21 algol kernel: [106030.533431] sda: detected capacity
change from 60022480896 to 0
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/4d36faf0.3010...@informatik.hu
Re: logcheck
SOLVED? so finally i grepped my whole fs. i found the olddomain in /var/cache/debconf/config.dat, with postfix owner(some main.cf values). what i did, run dpkg-reconfigure postfix. altough i have already changed the domain in postfix, mailname, etc, it showed up the old one. as i changed the domain via dpkg-reconf, it also changed in /var/cache/debconf/config.dat, and now logcheck is sending with the newdomain. postfix main.cf is identical before dpkg-reconfigure i can not imagine how can /var/cache/debconf/config.dat affect this! On 2011.01.19. 18:05, Camaleón wrote: El 2011-01-19 a las 12:10 +0100, Informatik.hu escribió: (resending to the list) On 2011.01.17. 16:04, Camaleón wrote: On Mon, 17 Jan 2011 14:41:11 +0100, Informatik.hu wrote: I am using logcheck on my squeeze, i have changed the domain name of the machine from olddomain.com to newdomain.com, everything works fine, but logcheck still sends the mails with r...@olddomain.com. How/where can i a change the sender of logcheck emails? In the configuration file /etc/logcheck/logcheck.conf there should be a variable SENDMAILTO= that you can adjust. But the main question still remains (unless you had manually changed the default settings of that variable and now forgot to update it ;-P)... Why e-mails to root are not delivered to the current and updated host domain? Check your alises database (cat /etc/alisases) and your hostname (hostname -d). NOT SOLVED! Still sending with olddomain. I tried to purge and reinstall logcheck package, but nothing. Sending with or sending to? I'm afraid this is not happening only with logcheck e-mails but all e-mails that pass through your Postfix server. Please, send a message to logcheck user and review the Postfix log to see what is going on. Greetings, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d37213c.4000...@informatik.hu
logcheck
Hi All! I am using logcheck on my squeeze, i have changed the domain name of the machine from olddomain.com to newdomain.com, everything works fine, but logcheck still sends the mails with r...@olddomain.com. How/where can i a change the sender of logcheck emails? Vuki -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d3446f7.5050...@informatik.hu
[solved/workaround] Re: logcheck
Hi! SENDMAILTO=logcheck in aliases logcheck:root root:szun szun:[where i wanted to send the logcheck mai] so i changed the sendmailto= to my destination email, and voila, it comes with the newdomain! any suugestions? On 2011.01.17. 16:04, Camaleón wrote: On Mon, 17 Jan 2011 14:41:11 +0100, Informatik.hu wrote: I am using logcheck on my squeeze, i have changed the domain name of the machine from olddomain.com to newdomain.com, everything works fine, but logcheck still sends the mails with r...@olddomain.com. How/where can i a change the sender of logcheck emails? In the configuration file /etc/logcheck/logcheck.conf there should be a variable SENDMAILTO= that you can adjust. But the main question still remains (unless you had manually changed the default settings of that variable and now forgot to update it ;-P)... Why e-mails to root are not delivered to the current and updated host domain? Check your alises database (cat /etc/alisases) and your hostname (hostname -d). Greetings, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d348bd0.8070...@informatik.hu
SSL Cert
Hi! Do you know a cheap, safe and well known trusted ssl certificate provider? I would like to use it with lighttpd, postfix and dovecot. thx! -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d27580a.2090...@informatik.hu
Re: SSL Cert
certs already installed, thanx! one more question: i would like to redirect https://*.mydomain.com to https://secure.mydomain.com in lighttpd. any suggestions? On 2011.01.07. 20:17, Camaleón wrote: On Fri, 07 Jan 2011 19:14:34 +0100, Informatik.hu wrote: Do you know a cheap, safe and well known trusted ssl certificate provider? I would like to use it with lighttpd, postfix and dovecot. This is what I use for apache2 (https), cyrus (pop3s/imaps) and postfix (smtps): http://www.rapidssl.com/ Greetings, -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d276e81.5070...@informatik.hu
lighttpd - fastcgi-php - php5-cgi
Hi! I would like use lighttpd with fastcgi-php. Fastcgi-php connects to php5-cgi on 127.0.0.1:521. I can start php5-cgi -b 127.0.0.1:521 with root, but i would like to run in with another user, like www-data. Exactly i want to run multiple php5-cgi with multiple user (different ports per virtual hosts). When i try to start php5-cgi with a normal user, i got the Cannot bind/listen socket - [13] Permission denied. Couldn't create FastCGI listen socket on port 127.0.0.1:522 How can i star php5-cgi with a normal, or reduced user? Vuki -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d24c03f.4050...@informatik.hu
Re: lighttpd - fastcgi-php - php5-cgi
It is working well! :) I was trying to make apache2 fcgid/fascgi with suexec or suphp working for two days.. :| With lighttpd + fastcgi_php + php5-cgi it is much more easy and fast! thanx! On 2011.01.05. 21:33, Bob Proulx wrote: Informatik.hu wrote: I would like use lighttpd with fastcgi-php. Fastcgi-php connects to php5-cgi on 127.0.0.1:521. I can start php5-cgi -b 127.0.0.1:521 with root, but i would like to run in with another user, like www-data. Ports below 1024 are available only to the root user. In order to use them with a non-root user you would need to pick a port above 1024. Exactly i want to run multiple php5-cgi with multiple user (different ports per virtual hosts). When i try to start php5-cgi with a normal user, i got the Cannot bind/listen socket - [13] Permission denied. Couldn't create FastCGI listen socket on port 127.0.0.1:522 Correct. To use port 521 or 522 it needs to be opened by the root user. This is a security restriction. How can i star php5-cgi with a normal, or reduced user? The best solution would be to pick a port above 1024. Bbo -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4d254ab7.2080...@informatik.hu
