Displaying 5 results from an estimated 5 matches for "vault2".
Did you mean:
vault
2017 Nov 06
0
ctdb vacuum timeouts and record locks
...> hm, I stand correct on the problem solved statement below. Ip addresses
> are simply not cooperating on the 2nd node.
>
> root at vault1:~# ctdb ip
> Public IPs on node 0
> 192.168.120.90 0
> 192.168.120.91 0
> 192.168.120.92 0
> 192.168.120.93 0
>
> root at vault2:/service/ctdb/log/main# ctdb ip
> Public IPs on node 1
> 192.168.120.90 0
> 192.168.120.91 0
> 192.168.120.92 0
> 192.168.120.93 0
>
> root at vault2:/service/ctdb/log/main# ctdb moveip 192.168.120.90 1
> Control TAKEOVER_IP failed, ret=-1
> Failed to takeover IP on node...
2007 May 08
0
Two Permissions Issues: null session shares and group membership
...re is defined as follows:
[open]
comment = Null Session Share
path = /pool/open
public = yes
browseable = yes
create mask = 0666
directory mask = 0777
guest account = nobody
force user = nobody
guest ok = yes
The directory is:
vault2:/pool#ls -al | grep open
drwxrwxrwx 2 nobody sys 2 May 8 11:16 open
vault2:/pool#
When I connect to the share with a valid AD user account, I receive the
following message on the client: "The specified user does not exist." The
log of the session on the server (snipped f...
2017 Nov 02
2
ctdb vacuum timeouts and record locks
hm, I stand correct on the problem solved statement below. Ip addresses
are simply not cooperating on the 2nd node.
root at vault1:~# ctdb ip
Public IPs on node 0
192.168.120.90 0
192.168.120.91 0
192.168.120.92 0
192.168.120.93 0
root at vault2:/service/ctdb/log/main# ctdb ip
Public IPs on node 1
192.168.120.90 0
192.168.120.91 0
192.168.120.92 0
192.168.120.93 0
root at vault2:/service/ctdb/log/main# ctdb moveip 192.168.120.90 1
Control TAKEOVER_IP failed, ret=-1
Failed to takeover IP on node 1
root at vault1:~# ctdb moveip 192.168.120...
2017 Oct 27
3
ctdb vacuum timeouts and record locks
Hi Martin,
Thanks for reading and taking the time to reply
>> ctdbd[89]: Unable to get RECORD lock on database locking.tdb for 20 seconds
>> /usr/local/samba/etc/ctdb/debug_locks.sh: 142:
>> /usr/local/samba/etc/ctdb/debug_locks.sh: cannot create : Directory
>> nonexistent
>> sh: echo: I/O error
>> sh: echo: I/O error
>
> That's weird. The only
2014 Oct 29
2
2.2.15 Panic in mbox_sync_read_next_mail()
It might not be a fault in dovecot, as the user is accessing the folder locally
with alpine while also running imap-sessions. However it would have been nice
with a more graceful action than panic?
The panic is preceeded by
Error: Next message unexpectedly corrupted in mbox file PATH
Panic: file mbox-sync.c: line 152 (mbox_sync_read_next_mail): assertion failed: