SWAT does not work after installing SAMBA 3.0.7 un HPUX11.1 V1

[Joachim Mangold_1]

Hello,
after installing CIFS-Server A.02.01 (base on Samba 3.0.7) SWAT will not start. In /var/opt/samba/log.swat the following errors can be found:
===============================================================
[2005/02/17 14:30:39, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 6 in pid 10618 (3.0.7 based HP CIFS Server A.02.01)
Please read the appendix Bugs of the Samba HOWTO collection
[2005/02/17 14:30:39, 0] lib/fault.c:fault_report(39)
===============================================================
[2005/02/17 14:30:39, 0] lib/util.c:smb_panic2(1381)
PANIC: internal error
[2005/02/17 14:30:43, 0] lib/fault.c:fault_report(36)
===============================================================
[2005/02/17 14:30:43, 0] lib/fault.c:fault_report(37)
INTERNAL ERROR: Signal 6 in pid 10625 (3.0.7 based HP CIFS Server A.02.01)
Please read the appendix Bugs of the Samba HOWTO collection
[2005/02/17 14:30:44, 0] lib/fault.c:fault_report(39)
===============================================================
[2005/02/17 14:30:44, 0] lib/util.c:smb_panic2(1381)
PANIC: internal error

Regards
Joachim

[RAC_1]

swat is not starting because, samba is not starting. Look for patches/or update to latest version. Unless you start samba successfully, you can start swat.

Anil

[Steven E. Protter]

I didn't do this but suggest the following:

swremove samba 3.0.7
swremove samba A2.0.1

Install samba 3.0.7 HP depot set.

Get samba to start.

Check swat.

You may need to modify the default smb.conf

To clarify, what I did not do was remove samba 2.x prior to installing samba 3.0.7 from HP's software.hp.com site.

SEP

[Steven E. Protter]

Duh.

Forget the depot stuff.

Remove samba, start over with the install. save your old smb.conf file for reference.

As noted by the guy above who was awake when he posted once samba starts swat will work.

Also, samba is on version 3.10, that would be a good idea as well.

SEP

[Simeon Harwood]

It might be worth looking in your smb.conf file to look for "allowed hosts" to see if you are allowed to see SWAT from form you client machine. If you have said that host "192.168.1.10" can see SAMBA, then you might not be able to see if from "192.168.1.20"
As a test, remove any entry for allow or deny, and see if that works.