I have website server hosted on digitalocean with Ubuntu 16.04, LAMP. So, when I need to have my own domain name email address, I followed this tutorial to create one. After going through the tutorial I was able to send a mail but could not receive because the squirrel browser interface says:
enter code here
ERROR: Could not complete request.
Query: SELECT "INBOX"
Reason Given: [SERVERBUG] Internal error occurred. Refer to server log for more information. [2018-08-22 03:58:59] (0.000 + 0.000 secs).
This is the error log
---------------------
Aug 22 03:44:58 haemocaregate dovecot: imap(daniolayinka): Error: open(/var/mail/daniolayinka) failed: Permission denied (euid=1003(daniolayinka) egi$
Aug 22 03:44:58 haemocaregate dovecot: imap(daniolayinka): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log fo$
Aug 22 03:44:59 haemocaregate dovecot: imap(daniolayinka): Error: open(/var/mail/daniolayinka) failed: Permission denied (euid=1003(daniolayinka) egi$
Aug 22 03:44:59 haemocaregate dovecot: imap(daniolayinka): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log fo$
Aug 22 03:49:40 haemocaregate dovecot: imap(daniolayinka): Error: open(/var/mail/daniolayinka) failed: Permission denied (euid=1003(daniolayinka) egi$
Aug 22 03:49:40 haemocaregate dovecot: imap(daniolayinka): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log fo$
Aug 22 03:49:40 haemocaregate dovecot: imap(daniolayinka): Error: open(/var/mail/daniolayinka) failed: Permission denied (euid=1003(daniolayinka) egi$
Aug 22 03:49:40 haemocaregate dovecot: imap(daniolayinka): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log fo$
Aug 22 03:58:03 haemocaregate dovecot: imap(daniolayinka): Error: open(/var/mail/daniolayinka) failed: Permission denied (euid=1003(daniolayinka) egi$
Aug 22 03:58:03 haemocaregate dovecot: imap(daniolayinka): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log fo$
Aug 22 03:58:03 haemocaregate dovecot: imap(daniolayinka): Error: open(/var/mail/daniolayinka) failed: Permission denied (euid=1003(daniolayinka) egi$
Aug 22 03:58:03 haemocaregate dovecot: imap(daniolayinka): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log fo$
Aug 22 03:58:10 haemocaregate dovecot: imap(daniolayinka): Error: open(/var/mail/daniolayinka) failed: Permission denied (euid=1003(daniolayinka) egi$
Aug 22 03:58:10 haemocaregate dovecot: imap(daniolayinka): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log fo$
Aug 22 03:58:59 haemocaregate dovecot: imap(daniolayinka): Error: open(/var/mail/daniolayinka) failed: Permission denied (euid=1003(daniolayinka) egi$
Aug 22 03:58:59 haemocaregate dovecot: imap(daniolayinka): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log fo$
Aug 22 03:58:59 haemocaregate dovecot: imap(daniolayinka): Error: open(/var/mail/daniolayinka) failed: Permission denied (euid=1003(daniolayinka) egi$
Aug 22 03:58:59 haemocaregate dovecot: imap(daniolayinka): Error: Failed to autocreate mailbox INBOX: Internal error occurred. Refer to server log fo$
From your logs, it is obvious that this is a permission issue. dovecot is trying to open a path /var/mail/daniolayinka which it can't access for one of two reasons:
The path exists but devcot cannot open it because of permission issues
The path does not exist and devcot does not have permission to create it
Solution:
If the path does not exist, create it and retry.
If the path does exist, then make sure you've set the right permissions. E.g you may run the following command. chmod -R 755 /var/mail/daniolayinka
Related
I have a Bluetooth remote that I have used before on another system and now running the 4.52 BLUEZ I get an error in bluetoothctl as soon as I paired with the remote.
Connecting to the bluetooth ctl
pi#marcophone:~$ sudo bluetoothctl
Agent registered
[CHG] Controller B8:27:EB:1B:C4:00 Pairable: yes
[CHG] Device 20:C3:8F:BD:93:40 Connected: yes
[Remote RC]# trust
Changing 20:C3:8F:BD:93:40 trust succeeded
Here I successfully connected to the remote
[RC]# pair
Attempting to pair with 20:C3:8F:BD:93:40
[CHG] Device 20:C3:8F:BD:93:40 Paired: yes
Pairing successful
Right after this the bluetoothctl looses the connection
[DEL] Descriptor (Handle 0x2ec8)
/org/bluez/hci0/dev_20_C3_8F_BD_93_40/service0008/char0009/desc000b
00002902-0000-1000-8000-00805f9b34fb
Client Characteristic Configuration
[DEL] Characteristic (Handle 0x4cf0)
/org/bluez/hci0/dev_20_C3_8F_BD_93_40/service0008/char0009
00002a05-0000-1000-8000-00805f9b34fb
Service Changed
[DEL] Primary Service (Handle 0x0073)
/org/bluez/hci0/dev_20_C3_8F_BD_93_40/service0008
00001801-0000-1000-8000-00805f9b34fb
Generic Attribute Profile
[DEL] Characteristic (Handle 0x4cf0)
/org/bluez/hci0/dev_20_C3_8F_BD_93_40/service000c/char000d
00002a50-0000-1000-8000-00805f9b34fb
PnP ID
[DEL] Primary Service (Handle 0x0073)
/org/bluez/hci0/dev_20_C3_8F_BD_93_40/service000c
0000180a-0000-1000-8000-00805f9b34fb
Device Information
Agent unregistered
[DEL] Controller B8:27:EB:1B:C4:00 marcophone [default]
Waiting to connect to bluetoothd...con
The Logs:
pi#marcophone:~$ cat /var/log/syslog | grep bluetooth -a
Jan 27 18:39:40 marcophone bluetoothd[1048]: Bluetooth daemon 5.52
Jan 27 18:39:40 marcophone bluetoothd[1048]: Starting SDP server
Jan 27 18:39:40 marcophone systemd[1]: Started Raspberry Pi bluetooth helper.
Jan 27 18:39:40 marcophone bluetoothd[1048]: Bluetooth management interface 1.14 initialized
Jan 27 18:39:40 marcophone bluetoothd[1048]: Endpoint registered: sender=:1.21 path=/A2DP/SBC/Source/1
Jan 27 18:39:40 marcophone bluetoothd[1048]: Failed to set privacy: Rejected (0x0b)
Jan 27 18:41:07 marcophone bluetoothd[1048]: No cache for 20:C3:8F:BD:93:40
Jan 27 18:41:12 marcophone bluetoothd[1048]: Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
Jan 27 18:41:13 marcophone bluetoothd[1048]: Report Map read failed: Request attribute has encountered an unlikely error
Jan 27 18:41:13 marcophone bluetoothd[1048]: Read External Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:13 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:13 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:13 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:13 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:13 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:13 marcophone bluetoothd[1048]: HID Information read failed: Request attribute has encountered an unlikely error
Jan 27 18:41:24 marcophone bluetoothd[1048]: Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
Jan 27 18:41:24 marcophone bluetoothd[1048]: Report Map read failed: Request attribute has encountered an unlikely error
Jan 27 18:41:24 marcophone bluetoothd[1048]: Read External Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:24 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:24 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:24 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:24 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:24 marcophone bluetoothd[1048]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:41:24 marcophone bluetoothd[1048]: Error storing included service - can't find it
Jan 27 18:41:24 marcophone systemd[1]: bluetooth.service: Main process exited, code=killed, status=11/SEGV
Jan 27 18:41:24 marcophone systemd[1]: bluetooth.service: Unit entered failed state.
Jan 27 18:41:24 marcophone systemd[1]: bluetooth.service: Failed with result 'signal'.
Jan 27 18:43:07 marcophone bluetoothd[356]: Bluetooth daemon 5.52
Jan 27 18:43:07 marcophone bluetoothd[356]: Starting SDP server
Jan 27 18:43:08 marcophone systemd[1]: Started Raspberry Pi bluetooth helper.
Jan 27 18:43:08 marcophone bluetoothd[356]: Bluetooth management interface 1.14 initialized
Jan 27 18:43:08 marcophone bluetoothd[356]: Endpoint registered: sender=:1.5 path=/A2DP/SBC/Source/1
Jan 27 18:43:08 marcophone bluetoothd[356]: Failed to set privacy: Rejected (0x0b)
Jan 27 18:45:11 marcophone bluetoothd[356]: No cache for 20:C3:8F:BD:93:40
Jan 27 18:45:11 marcophone bluetoothd[356]: BATT attribute not found
Jan 27 18:45:11 marcophone bluetoothd[356]: batt-profile profile accept failed for 20:C3:8F:BD:93:40
Jan 27 18:45:11 marcophone bluetoothd[356]: GAP attribute not found
Jan 27 18:45:11 marcophone bluetoothd[356]: gap-profile profile accept failed for 20:C3:8F:BD:93:40
Jan 27 18:45:11 marcophone bluetoothd[356]: input-hog profile accept failed for 20:C3:8F:BD:93:40
Jan 27 18:45:14 marcophone bluetoothd[356]: HID Information read failed: Request attribute has encountered an unlikely error
Jan 27 18:45:14 marcophone bluetoothd[356]: Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
Jan 27 18:45:14 marcophone bluetoothd[356]: Report Map read failed: Request attribute has encountered an unlikely error
Jan 27 18:45:14 marcophone bluetoothd[356]: Read External Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:14 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:14 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:14 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:14 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:14 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:17 marcophone bluetoothd[356]: HID Information read failed: Request attribute has encountered an unlikely error
Jan 27 18:45:17 marcophone bluetoothd[356]: Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
Jan 27 18:45:17 marcophone bluetoothd[356]: Report Map read failed: Request attribute has encountered an unlikely error
Jan 27 18:45:17 marcophone bluetoothd[356]: Read External Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:17 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:18 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:18 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:18 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:18 marcophone bluetoothd[356]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:45:18 marcophone bluetoothd[356]: Error storing included service - can't find it
Jan 27 18:45:18 marcophone systemd[1]: bluetooth.service: Main process exited, code=killed, status=11/SEGV
Jan 27 18:45:18 marcophone systemd[1]: bluetooth.service: Unit entered failed state.
Jan 27 18:45:18 marcophone systemd[1]: bluetooth.service: Failed with result 'signal'.
Jan 27 18:54:00 marcophone bluetoothd[358]: Bluetooth daemon 5.52
Jan 27 18:54:00 marcophone bluetoothd[358]: Starting SDP server
Jan 27 18:54:00 marcophone systemd[1]: Started Raspberry Pi bluetooth helper.
Jan 27 18:54:00 marcophone bluetoothd[358]: Bluetooth management interface 1.14 initialized
Jan 27 18:54:01 marcophone bluetoothd[358]: Endpoint registered: sender=:1.5 path=/A2DP/SBC/Source/1
Jan 27 18:54:01 marcophone bluetoothd[358]: Failed to set privacy: Rejected (0x0b)
Jan 27 18:55:30 marcophone bluetoothd[358]: No cache for 20:C3:8F:BD:93:40
Jan 27 18:55:30 marcophone bluetoothd[358]: BATT attribute not found
Jan 27 18:55:30 marcophone bluetoothd[358]: batt-profile profile accept failed for 20:C3:8F:BD:93:40
Jan 27 18:55:30 marcophone bluetoothd[358]: GAP attribute not found
Jan 27 18:55:31 marcophone bluetoothd[358]: gap-profile profile accept failed for 20:C3:8F:BD:93:40
Jan 27 18:55:31 marcophone bluetoothd[358]: input-hog profile accept failed for 20:C3:8F:BD:93:40
Jan 27 18:55:36 marcophone bluetoothd[358]: Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
Jan 27 18:55:36 marcophone bluetoothd[358]: Report Map read failed: Request attribute has encountered an unlikely error
Jan 27 18:55:36 marcophone bluetoothd[358]: Read External Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:36 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:36 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:36 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:36 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:36 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:36 marcophone bluetoothd[358]: HID Information read failed: Request attribute has encountered an unlikely error
Jan 27 18:55:47 marcophone bluetoothd[358]: Protocol Mode characteristic read failed: Request attribute has encountered an unlikely error
Jan 27 18:55:47 marcophone bluetoothd[358]: Report Map read failed: Request attribute has encountered an unlikely error
Jan 27 18:55:47 marcophone bluetoothd[358]: Read External Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:47 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:47 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:47 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:47 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:47 marcophone bluetoothd[358]: Read Report Reference descriptor failed: Request attribute has encountered an unlikely error
Jan 27 18:55:48 marcophone bluetoothd[358]: Error storing included service - can't find it
Jan 27 18:55:48 marcophone systemd[1]: bluetooth.service: Main process exited, code=killed, status=11/SEGV
Jan 27 18:55:48 marcophone systemd[1]: bluetooth.service: Unit entered failed state.
Jan 27 18:55:48 marcophone systemd[1]: bluetooth.service: Failed with result 'signal'.
Hciconfig
pi#marcophone:~$ hciconfig -a
hci0: Type: Primary Bus: UART
BD Address: B8:27:EB:1B:C4:00 ACL MTU: 1021:8 SCO MTU: 64:1
UP RUNNING
RX bytes:2850 acl:94 sco:0 events:117 errors:0
TX bytes:3820 acl:92 sco:0 commands:62 errors:0
Features: 0xbf 0xfe 0xcf 0xfe 0xdb 0xff 0x7b 0x87
Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
Link policy: RSWITCH SNIFF
Link mode: SLAVE ACCEPT
Name: 'marcophone'
Class: 0x480000
Service Classes: Capturing, Telephony
Device Class: Miscellaneous,
HCI Version: 4.1 (0x7) Revision: 0x168
LMP Version: 4.1 (0x7) Subversion: 0x2209
Manufacturer: Broadcom Corporation (15)
Versions:
pi#marcophone:~$ sudo bluetoothctl -v
sudo: Hostname marcophone kann nicht aufgelöst werden
bluetoothctl: 5.52
pi#marcophone:~$
Also I should see an entry here: /dev/input/event* but there is only /dev/input/mice.
I know that I got this working in bluez 5.50 so it could be an issue in bluez 5.52.
Doing the research I did add the following three options to my /lib/systemd/system/bluetooth.service:
ExecStart=/usr/libexec/bluetooth/bluetoothd --compat --noplugin=sap -E
I got this working on another machine. However that machine runs raspbian buster (4.19.97+ #1294 Thu Jan 30 13:10:54 GMT 2020 armv6l GNU/Linux).
I got some troubles connecting and paring with the remote so I did the following which finally got it working:
Update the system
sudo apt update && sudo apt upgrade
Update to the latest bluez stack
sudo apt-get remove bluez
date && sudo apt-get update && sudo apt-get install libdbus-1-dev libglib2.0-dev libudev-dev libical-dev libreadline-dev -y &&
date && wget www.kernel.org/pub/linux/bluetooth/bluez-5.52.tar.xz && tar xvf bluez-5.52.tar.xz &&
date && cd bluez-5.52 && ./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc --localstatedir=/var --enable-experimental && make -j4 && sudo make install && date && sudo reboot
Now update the ExecStart part of the service /lib/systemd/system/bluetooth.service as follows:
ExecStart=/usr/lib/bluetooth/bluetoothd --compat --noplugin=sap -E
Also update the /etc/bluetooth/main.conf and set Privacy = off in [General] section.
to upgrade to a newer bluez stack I would rather use packages, as follows
sudo apt install debhelper autotools-dev dh-autoreconf \
flex bison libdbus-glib-1-dev libglib2.0-dev \
libcap-ng-dev udev libudev-dev libreadline-dev \
libical-dev check dh-systemd libebook1.2-dev
mkdir bluez
cd bluez
wget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/bluez/5.55-0ubuntu1.1/bluez_5.55-0ubuntu1.1.dsc
wget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/bluez/5.55-0ubuntu1.1/bluez_5.55.orig.tar.xz
wget https://launchpad.net/ubuntu/+archive/primary/+sourcefiles/bluez/5.55-0ubuntu1.1/bluez_5.55-0ubuntu1.1.debian.tar.xz
dpkg-source -x bluez_5.55-0ubuntu1.1.dsc
cd bluez-5.55
dpkg-buildpackage -b
cd ..
sudo dpkg -i *deb
Using packages has the advantage that you can install other versions of this stuff
Running mongodb in docker container on raspbian.
If i run "service mongodb status" in container, it says mongodb is not running.
But if i look at ps aux it shows the process to be running.
This is from the log
Tue Feb 20 02:34:08.166 [initandlisten] ERROR: listen(): bind() failed errno:98 Address already in use for socket: 127.0.0.1:27017
Tue Feb 20 02:34:08.166 [websvr] ERROR: listen(): bind() failed errno:98 Address already in use for socket: 127.0.0.1:28017
Tue Feb 20 02:34:08.166 [initandlisten] ERROR: addr already in use
Tue Feb 20 02:34:08.166 [websvr] ERROR: addr already in use
Tue Feb 20 02:34:08.166 [initandlisten] now exiting
service mongodb start fails
What is going on with the service?
I tried rhn_register command to register for Red Hat(RHEL5).
Later I got the screen saying...
But after few minutes I got the screen saying can't connect the Red hat.
When I checked the /var/log/up2date file , below is the tail output
[root#mdw ~]# tail -f /var/log/up2date
[Mon Oct 24 23:54:36 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #1
[Mon Oct 24 23:56:01 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #2
[Mon Oct 24 23:57:26 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #3
[Mon Oct 24 23:58:51 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #4
[Tue Oct 25 00:00:16 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #5
[Tue Oct 25 00:25:25 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #1
[Tue Oct 25 00:26:50 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #2
[Tue Oct 25 00:28:15 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #3
[Tue Oct 25 00:29:40 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #4
[Tue Oct 25 00:31:05 2016] rhn_register A socket error occurred: (-3, 'Temporary failure in name resolution'), attempt #5
By looking at the /var/log/up2date file, it seems some problem with name resolution (not sure). Can someone please help me on this.
Thanks in advance.
I have one applicaion server having multiple nodes. When I am connecting the application through application server, it is working fine. But when I am connecting the application through webserver, it is not working for one node and for all other nodes it works.
What would be the possible cause. I have re-configured the plugin for that particular node many a times. no luck.
I see below logs in plugin log (date may change):
*[Mon Aug 10 11:53:50 2009] 00001dec 00001e04 - ERROR: ws_common: websphereGetStream: Failed to connect to app server on host 'windowsinternal.pt', OS err=78
[Mon Aug 10 11:53:51 2009] 00001dec 00001e04 - ERROR: ws_common: websphereGetStream: Failed to connect to app server on host 'windowsinternal.pt', OS err=78
[Mon Aug 10 11:53:51 2009] 00001dec 00001e04 - ERROR: ws_common: websphereExecute: Failed to create the stream
[Mon Aug 10 11:53:51 2009] 00001dec 00001e04 - ERROR: ws_common: websphereHandleRequest: Failed to execute the transaction to 'windowsinternalNode01_server1'on host 'windowsinternal.pt'; will try another one
[Mon Aug 10 11:53:51 2009] 00001dec 00001e04 - ERROR: ws_common: websphereWriteRequestReadResponse: Failed to find an app server to handle this request
[Mon Aug 10 11:53:51 2009] 00001dec 00001e04 - ERROR: ESI: getResponse: failed to get response: rc = 2
[Mon Aug 10 11:53:51 2009] 00001dec 00001e04 - ERROR: ws_common: websphereHandleRequest: Failed to handle request
[Mon Aug 10 11:53:52 2009] 00001dec 000015b4 - ERROR: ws_common: websphereGetStream: Failed to connect to app server on host 'windowsinternal.pt', OS err=78*
this issue was resolved. There was firewall issue with the default secure port. I just changed the port and it worked.
so im trying to dump a collection on mongodump through stdout so i can directly pipe it and gzip it. But it's giving me errors.
When i do:
mongodump --db test -u username -p Password -h mymongodatabase.onthecloud:12888 -vvvvv --collection posts --out -
it displays these errors:
Wed Feb 29 21:48:13 creating new connection to:mymongodatabase.onthecloud:12888
Wed Feb 29 21:48:13 BackgroundJob starting: ConnectBG
Wed Feb 29 21:48:13 connected connection!
connected to: mymongodatabase.onthecloud:12888
Wed Feb 29 21:48:13 nextSafe(): { $err: "unauthorized db:test lock type:-1 client:10.3.55.10", code: 10057 }
Wed Feb 29 21:48:13 User Assertion: 13106:nextSafe(): { $err: "unauthorized db:test lock type:-1 client:10.3.55.10", code: 10057 }
assertion: 13106 nextSafe(): { $err: "unauthorized db:test lock type:-1 client:10.3.55.10", code: 10057 }
but when i dunt include '--out -' it dumps the collection fine (doesn't give me aunauthorized error). What's going on?
it was a bug, issued and fixed:
https://jira.mongodb.org/browse/SERVER-5233