Freebsd 8 installation

[Boter]

Code:

login name `vu2000' already exists

Looks like it exists

[BeNe]

Did you enable mod_fcgid or mod_fastcgi ?
Your proftpd.conf now exists on the System ?

Greez BeNe

[Boter]

Code:

i choosed fastcgi in installation of the script. Conf is now at "/usr/local/etc/proftpd.conf"

I think some of the things are still missing. I get errors like

postfix/smtpd[1665]: SQL_select option missing
postfix/smtpd[1665]: auxpropfunk error no mechanism available

And on admin/server_status.php
Most of the things are "down"

amavis, dns, pop3-ssl, postgrey, and spamassasin.

But it looks DNS is running, according to

Code:

bind       792  0.0  1.4 16412 10764  ??  Is    9:14AM   0:00.09 /usr/sbin/named -t /var/named -u bind
root       802  0.0  0.2  3376  1404  ??  Ss    9:14AM   0:00.02 /usr/sbin/rpcbind

Btw maybe this will be helpful:

Code:

raindrop# uname -a
FreeBSD raindrop.home.lan 8.0-RELEASE FreeBSD 8.0-RELEASE #0: Sat Nov 21 15:48:17 UTC 2009     root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC  i386

[BeNe]

Code:

postfix/smtpd[1665]: SQL_select option missing
postfix/smtpd[1665]: auxpropfunk error no mechanism available

I know these Errors, but your Mailsystem works or ?

Quote:And on admin/server_status.php
Most of the things are "down"

amavis, dns, pop3-ssl, postgrey, and spamassasin.

This is more or less ok!
We install AMaVis but not enabled it per default, same with spamassasin.
Please check your /etc/rc.conf
Pop3-SSL is also disabled per default because it needs a Certificate!
Postgrey is descibed in the HowTO --> http://www.isp-control.net/documentation...t_-_log_in
You read that ?

Greez BeNe

[Boter]

Ok now I think I figured it... There's a typo

Code:

To enable it set this in your /etc/sysclt.conf on the Host:

Will check for mailsystem - no domains currently for which should it work.

security.jail.sysvipc_allowed is still 0 (edited /etc/sysctl.conf and /etc/defaults/rc.conf)

[server801]

dmesg -a

Quote:Starting named.
Apr 2 14:37:30 staynet named[736]: the working directory is not writable

in panel

Quote:sys_command() | ERROR: External command '/bin/echo n | /bin/cp -ip /usr/local/www/ispcp/gui/errordocs/401.html /usr/local/www/data/virtual/domain.ltd/errors/ 2>/dev/null' returned '1' status !

what is bug?
FreeBSD 8.0 Stable IspCP 1.0.5

[Boter]

Code:

Connection for controluser as defined in your configuration failed.

That's in phpmyadmin. Ispcp's fault?

---

Hm, I generated new reports. I tryed to update the script, but everything got broken, so I tried to install from ispcp-setup

Now I get

Code:

ERROR: External command '/usr/bin/newaliases >> /tmp/ispcp-setup-services.log 2>&1' returned '126' status !

error log from ispcp is

Code:

raindrop# cat /tmp/*.log
[System Init configuration:]
[FastCGI - Apache module configuration:]
[Postfix configuration:]
[Rkhunter & Sendmail configuration:]
[Cron configuration:]
/usr/bin/newaliases: Permission denied
postalias: fatal: open /usr/local/etc/postfix/aliases: No such file or directory

Any idea? How to make completely "clean" installation of ispcp overwriting what has been done earlier?

[BeNe]

(04-02-2010 08:42 PM)server801 Wrote:  dmesg -a

Quote:Starting named.
Apr 2 14:37:30 staynet named[736]: the working directory is not writable

in panel

Quote:sys_command() | ERROR: External command '/bin/echo n | /bin/cp -ip /usr/local/www/ispcp/gui/errordocs/401.html /usr/local/www/data/virtual/domain.ltd/errors/ 2>/dev/null' returned '1' status !

what is bug?
FreeBSD 8.0 Stable IspCP 1.0.5

To your named problem. I search around the web and this is more or less a FreeBSD problem, not an ispCP problem. There are many workaround like chown or chmod. But this solved the "problem" not in all cases. The most User talk about a "warning" and not a problem. Maybe you can try to find a soultion ?

The other problem, try to execute the command manually on the shell:

Code:

/bin/echo n | /bin/cp -ip /usr/local/www/ispcp/gui/errordocs/401.html /usr/local/www/data/virtual/domain.ltd/errors/ 2>/dev/null

I have this feeling that the "2>/dev/null" is the problem. Remove it please and try it again manually.

Code:

Connection for controluser as defined in your configuration failed.

Have the same under Debian! We need to check this point, too.
To the Update problem - you didn't run the update-script ? Only the ispcp-setup ?
I tested the Update script as well and it works fine for me.

What was the reason for your new installation ?

Greez BeNe

[Boter]

I couldn't delete added users from the ispcp, some conf. files for domains was generated wrong

[server801]

HI
At domain addition http://domain.ltd/reseller/user_add3.php - page

Code:

00000 - -

Code:

ll /usr/local/www/data/virtual
total 0

but

Code:

uname -a
FreeBSD xxxx.ru 8.1-STABLE FreeBSD 8.1-STABLE #0: Tue Aug 10 18:55:16 MSD 2010     root@xxxxxxxx.ru:/usr/obj/usr/src/sys/GENERIC  i386

ISP 1.06