The introduction to new ui requires boolean data.

Bot being botty.  Or spewing some blather about nothingness.

I take it you haven't encountered this problem then.

another:/root # cd /root
another:/root # /etc/init.d/postgresql92 rebuild
Rebuilding PostgreSQL database, all reporting data will be lost!
Enter "yes" to continue...
yes
:: Stopping PostgreSQLcould not change directory to "/root"
done
:: Initializing the PostgreSQL databasecould not change directory to "/root"
done
:: Starting PostgreSQL done
:: Restarting SMTP Proxy
:: Stopping SMTP Proxy
[ ok ]
:: Starting SMTP Proxy
[ ok ]
[ ok ]
another:/root #

No change

Hi John and welcome to the UTM community!

You need to execute the command as root.

Cheers - Bob

I did!

Ah, then the same underlying problem is probably causing "connection refused" and "could not change."  Please let us know what Sophos Support has to say about this.

Cheers - Bob

It is a home license. No access to Sophos support. I guess I will have to live with the problem.

Maybe Raphael Alganes can help you with that one.  He's been lurking here lately.

Essentially this sounds like a confd problem. The value in the current confd seems to be corrupt. psgl rebuild will not help, as it does only the reporting data base. 

This would mean, to investigate the entire cc database and find the broken value and to be honest. The best way to solve this would be a reinstallation plus restore of the backup. But the error could also be in the backup. 

I have tried reinstalling in the past so the error remains in the backup. i can live with the problem.

John, can you find anything in a Linux forum about could not change directory to "/root"?

Then again, did you su to a different user after logging in as root - that would explain why you're in the /root directory but don't have the right permissions.

Cheers - Bob

I su -  to root from loginuser.. Within that script I think I su to postgres . Is it that user that does not have permission to /root.

I su -  to root from loginuser.. Within that script I think I su to postgres . Is it that user that does not have permission to /root.

I don't think you can apply the fix above if you are user postgres - you need to be root.

Cheers - Bob