I installed ciphermail on CentOS following the quick install guide
step-by-step. Now when I try to access the Web GUI and login I get the
error:
Back-end is not running or not yet fully started up
I don't really know what exactly that means and a look in the
djigzo.log is more confusing for me.
I attach parts of the djigzo.log, maybe someone has an idea of what's
wrong.
I installed ciphermail on CentOS following the quick install guide
step-by-step. Now when I try to access the Web GUI and login I get the
error:
Back-end is not running or not yet fully started up
I don't really know what exactly that means and a look in the
djigzo.log is more confusing for me.
I attach parts of the djigzo.log, maybe someone has an idea of what's
wrong.
It looks like the back-end is not allowed to access the Postgres server.
exactly that line is written at the end of my php_hba.conf
host all all 127.0.0.1/32 md5
Best regards,
Samuel
···
Am 23.11.2015 um 10:16 schrieb Martijn Brinkers:
On 11/23/2015 10:10 AM, Samuel Greiner wrote:
Hey there,
I installed ciphermail on CentOS following the quick install
guide step-by-step. Now when I try to access the Web GUI and
login I get the error: Back-end is not running or not yet fully
started up
I don't really know what exactly that means and a look in the
djigzo.log is more confusing for me. I attach parts of the
djigzo.log, maybe someone has an idea of what's wrong.
It looks like the back-end is not allowed to access the Postgres
server.
exactly that line is written at the end of my php_hba.conf
host all all 127.0.0.1/32 md5
Is the Postgres database running on the same server as the gateway?
What is the output of the following command:
ip a
Kind regards,
Martijn Brinkers
···
On 11/23/2015 04:53 PM, Samuel Greiner wrote:
Am 23.11.2015 um 10:16 schrieb Martijn Brinkers:
On 11/23/2015 10:10 AM, Samuel Greiner wrote:
Hey there,
I installed ciphermail on CentOS following the quick install
guide step-by-step. Now when I try to access the Web GUI and
login I get the error: Back-end is not running or not yet fully
started up
I don't really know what exactly that means and a look in the
djigzo.log is more confusing for me. I attach parts of the
djigzo.log, maybe someone has an idea of what's wrong.
It looks like the back-end is not allowed to access the Postgres
server.
Output of ip a:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
qlen 1000
link/ether a0:48:1c:b8:96:50 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.254/24 brd 192.168.1.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::a248:1cff:feb8:9650/64 scope link
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
qlen 1000
link/ether a0:48:1c:b8:96:51 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.99/24 brd 192.168.0.255 scope global eno2
valid_lft forever preferred_lft forever
inet6 fe80::a248:1cff:feb8:9651/64 scope link
valid_lft forever preferred_lft forever
Thanks and best regards,
Samuel
···
Am 23.11.2015 um 17:00 schrieb Martijn Brinkers:
On 11/23/2015 04:53 PM, Samuel Greiner wrote:
exactly that line is written at the end of my php_hba.conf
host all all 127.0.0.1/32
md5
Is the Postgres database running on the same server as the
gateway?
What is the output of the following command:
ip a
Kind regards,
Martijn Brinkers
Am 23.11.2015 um 10:16 schrieb Martijn Brinkers:
On 11/23/2015 10:10 AM, Samuel Greiner wrote:
Hey there,
I installed ciphermail on CentOS following the quick install
guide step-by-step. Now when I try to access the Web GUI and
login I get the error: Back-end is not running or not yet
fully started up
I don't really know what exactly that means and a look in the
djigzo.log is more confusing for me. I attach parts of the
djigzo.log, maybe someone has an idea of what's wrong.
It looks like the back-end is not allowed to access the
Postgres server.
Output of ip a:
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
valid_lft forever preferred_lft forever
inet6 ::1/128 scope host
valid_lft forever preferred_lft forever
2: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
qlen 1000
link/ether a0:48:1c:b8:96:50 brd ff:ff:ff:ff:ff:ff
inet 192.168.1.254/24 brd 192.168.1.255 scope global eno1
valid_lft forever preferred_lft forever
inet6 fe80::a248:1cff:feb8:9650/64 scope link
valid_lft forever preferred_lft forever
3: eno2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
qlen 1000
link/ether a0:48:1c:b8:96:51 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.99/24 brd 192.168.0.255 scope global eno2
valid_lft forever preferred_lft forever
inet6 fe80::a248:1cff:feb8:9651/64 scope link
valid_lft forever preferred_lft forever
According to the log, it seems that the connection to Postgres is coming
from 192.168.1.254 and not from 127.0.0.1 (localhost). Not sure why this
happens.
Can you try to add the following line to pg_hba.conf to see whether this
works? :
host all all 192.168.1.254/32 md5
Kind regards,
Martijn Brinkers
···
On 11/23/2015 05:05 PM, Samuel Greiner wrote:
Am 23.11.2015 um 17:00 schrieb Martijn Brinkers:
On 11/23/2015 04:53 PM, Samuel Greiner wrote:
exactly that line is written at the end of my php_hba.conf
host all all 127.0.0.1/32
md5
Is the Postgres database running on the same server as the
gateway?
What is the output of the following command:
ip a
Kind regards,
Martijn Brinkers
Am 23.11.2015 um 10:16 schrieb Martijn Brinkers:
On 11/23/2015 10:10 AM, Samuel Greiner wrote:
Hey there,
I installed ciphermail on CentOS following the quick install
guide step-by-step. Now when I try to access the Web GUI and
login I get the error: Back-end is not running or not yet
fully started up
I don't really know what exactly that means and a look in the
djigzo.log is more confusing for me. I attach parts of the
djigzo.log, maybe someone has an idea of what's wrong.
It looks like the back-end is not allowed to access the
Postgres server.
Output of ip a: 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc
noqueue state UNKNOWN link/loopback 00:00:00:00:00:00 brd
00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft
forever preferred_lft forever inet6 ::1/128 scope host valid_lft
forever preferred_lft forever 2: eno1:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
1000 link/ether a0:48:1c:b8:96:50 brd ff:ff:ff:ff:ff:ff inet
192.168.1.254/24 brd 192.168.1.255 scope global eno1 valid_lft
forever preferred_lft forever inet6 fe80::a248:1cff:feb8:9650/64
scope link valid_lft forever preferred_lft forever 3: eno2:
<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen
1000 link/ether a0:48:1c:b8:96:51 brd ff:ff:ff:ff:ff:ff inet
192.168.0.99/24 brd 192.168.0.255 scope global eno2 valid_lft
forever preferred_lft forever inet6 fe80::a248:1cff:feb8:9651/64
scope link valid_lft forever preferred_lft forever
According to the log, it seems that the connection to Postgres is
coming from 192.168.1.254 and not from 127.0.0.1 (localhost). Not
sure why this happens.
Can you try to add the following line to pg_hba.conf to see whether
this works? :
host all all 192.168.1.254/32
md5
Kind regards,
Martijn Brinkers
Am 23.11.2015 um 17:00 schrieb Martijn Brinkers:
On 11/23/2015 04:53 PM, Samuel Greiner wrote:
exactly that line is written at the end of my php_hba.conf
host all all 127.0.0.1/32 md5
Is the Postgres database running on the same server as the
gateway?
What is the output of the following command:
ip a
Kind regards,
Martijn Brinkers
Am 23.11.2015 um 10:16 schrieb Martijn Brinkers:
On 11/23/2015 10:10 AM, Samuel Greiner wrote:
Hey there,
I installed ciphermail on CentOS following the quick
install guide step-by-step. Now when I try to access the
Web GUI and login I get the error: Back-end is not
running or not yet fully started up
I don't really know what exactly that means and a look in
the djigzo.log is more confusing for me. I attach parts
of the djigzo.log, maybe someone has an idea of what's
wrong.
It looks like the back-end is not allowed to access the
Postgres server.