Displaying 5 results from an estimated 5 matches for "primary_hostnam".
Did you mean:
primary_hostname
2017 Sep 15
3
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...660 with 16GB RAM virtualised on XenServer 7.2
root at int-gluster-03:~ # gluster get
glusterd state dumped to /var/run/gluster/glusterd_state_20170915_110532
[Global]
MYUUID: 0b42ffb2-217a-4db6-96bf-cf304a0fa1ae
op-version: 31200
[Global options]
cluster.brick-multiplex: enable
[Peers]
Peer1.primary_hostname: int-gluster-02.fqdn.here
Peer1.uuid: e614686d-0654-43c9-90ca-42bcbeda3255
Peer1.state: Peer in Cluster
Peer1.connected: Connected
Peer1.othernames:
Peer2.primary_hostname: int-gluster-01.fqdn.here
Peer2.uuid: 9b0c82ef-329d-4bd5-92fc-95e2e90204a6
Peer2.state: Peer in Cluster
Peer2.connected: Conne...
2017 Sep 18
2
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...lusterd state dumped to /var/run/gluster/glusterd_state_20170915_110532
>>
>> [Global]
>> MYUUID: 0b42ffb2-217a-4db6-96bf-cf304a0fa1ae
>> op-version: 31200
>>
>> [Global options]
>> cluster.brick-multiplex: enable
>>
>> [Peers]
>> Peer1.primary_hostname: int-gluster-02.fqdn.here
>> Peer1.uuid: e614686d-0654-43c9-90ca-42bcbeda3255
>> Peer1.state: Peer in Cluster
>> Peer1.connected: Connected
>> Peer1.othernames:
>> Peer2.primary_hostname: int-gluster-01.fqdn.here
>> Peer2.uuid: 9b0c82ef-329d-4bd5-92fc-95e2e90204...
2017 Sep 18
0
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...t at int-gluster-03:~ # gluster get
> glusterd state dumped to /var/run/gluster/glusterd_state_20170915_110532
>
> [Global]
> MYUUID: 0b42ffb2-217a-4db6-96bf-cf304a0fa1ae
> op-version: 31200
>
> [Global options]
> cluster.brick-multiplex: enable
>
> [Peers]
> Peer1.primary_hostname: int-gluster-02.fqdn.here
> Peer1.uuid: e614686d-0654-43c9-90ca-42bcbeda3255
> Peer1.state: Peer in Cluster
> Peer1.connected: Connected
> Peer1.othernames:
> Peer2.primary_hostname: int-gluster-01.fqdn.here
> Peer2.uuid: 9b0c82ef-329d-4bd5-92fc-95e2e90204a6
> Peer2.state: Pee...
2017 Sep 25
0
0-client_t: null client [Invalid argument] & high CPU usage (Gluster 3.12)
...lusterd state dumped to /var/run/gluster/glusterd_state_20170915_110532
>>
>> [Global]
>> MYUUID: 0b42ffb2-217a-4db6-96bf-cf304a0fa1ae
>> op-version: 31200
>>
>> [Global options]
>> cluster.brick-multiplex: enable
>>
>> [Peers]
>> Peer1.primary_hostname: int-gluster-02.fqdn.here
>> Peer1.uuid: e614686d-0654-43c9-90ca-42bcbeda3255
>> Peer1.state: Peer in Cluster
>> Peer1.connected: Connected
>> Peer1.othernames:
>> Peer2.primary_hostname: int-gluster-01.fqdn.here
>> Peer2.uuid: 9b0c82ef-329d-4bd5-92fc-95e2e90204...
2013 Dec 25
2
LMTP with virtual and system users
Hi,
I have a mailsystem where i have some local users with shell access and
full home dirs which receive mail and also several SQL virtual users
only for mail.
With the virtual users, everything works fine. Mail is delivered via
LMTP and also sieve works :)
The SQL Lookup knows what to do with username at domain.com
The problem is the system user. If exim delivers the mail to the lmtp