I am configuring the Apache james Server, But fail to start the server.
please help.Thanks in Advance.
Followed Steps:
C:\xampp\htdocs\apache-james-3.0-beta4\bin>j
wrapper | Apache James Server App installed
C:\xampp\htdocs\apache-james-3.0-beta4\bin>j
wrapper | Starting the Apache James Server
wrapper | Waiting to start...
wrapper | The Apache James Server App servi
Press any key to continue . . .
C:\xampp\htdocs\apache-james-3.0-beta4\bin>
james-server.log
INFO 12:12:51,775 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#2ba11895: startup date [Sat Apr 23 12:12:51 IST 2016]; root of context hierarchy
INFO 12:13:12,034 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#5a8d9005: startup date [Sat Apr 23 12:13:12 IST 2016]; root of context hierarchy
INFO 12:14:16,123 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#2ba11895: startup date [Sat Apr 23 12:14:16 IST 2016]; root of context hierarchy
INFO 12:17:01,778 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#356cdec9: startup date [Sat Apr 23 12:17:01 IST 2016]; root of context hierarchy
INFO 12:19:37,360 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#2ba11895: startup date [Sat Apr 23 12:19:37 IST 2016]; root of context hierarchy
INFO 12:25:51,556 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#17c68925: startup date [Sat Apr 23 12:25:51 IST 2016]; root of context hierarchy
INFO 12:26:17,151 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#17c68925: startup date [Sat Apr 23 12:26:17 IST 2016]; root of context hierarchy
INFO 12:26:33,036 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#17c68925: startup date [Sat Apr 23 12:26:33 IST 2016]; root of context hierarchy
INFO 12:30:06,836 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#2ba11895: startup date [Sat Apr 23 12:30:06 IST 2016]; root of context hierarchy
INFO 12:32:47,145 | org.apache.james.container.spring.context.JamesServerApplicationContext | Refreshing org.apache.james.container.spring.context.JamesServerApplicationContext#356cdec9: startup date [Sat Apr 23 12:32:47 IST 2016]; root of context hierarchy
Related
link:-https://github.com/jonathanzufi/SignalR-ReactNativeClient
using this library and getting error in building connection
error: [2021-10-21T11:37:44.853Z] Debug: Starting HubConnection.
[Thu Oct 21 2021 17:07:43.711] LOG [2021-10-21T11:37:44.854Z] Debug: Starting connection with transfer format 'Text'.
[Thu Oct 21 2021 17:07:43.712] LOG [2021-10-21T11:37:44.855Z] Debug: Sending negotiation request: https://signalrdemo.com/chatHub/negotiate?negotiateVersion=1.
[Thu Oct 21 2021 17:07:43.714] LOG {"_40": 0, "_55": null, "_65": 0, "_72": null} connect
[Thu Oct 21 2021 17:07:43.721] WARN [2021-10-21T11:37:44.887Z] Warning: Error from HTTP request. 0: undefined.
[Thu Oct 21 2021 17:07:43.772] LOG Global error handler
[Thu Oct 21 2021 17:07:43.818] LOG Global error handler
[Thu Oct 21 2021 17:07:43.820] LOG [2021-10-21T11:37:44.946Z] Debug: HubConnection failed to start successfully because of error 'Error'.
[Thu Oct 21 2021 17:07:43.820] LOG [Error] err::::::::::::::
[Thu Oct 21 2021 17:07:43.821] LOG Error starting the connection: Error
technology used :-react-native
I have an all-in-one-setup with my controller and compute services running on the same node.all my nova and other dependent services are up and running. However, when i try to launch an instance the state of the nova-compute process becomes down. Because of this the instance is stuck in spawning state.
> [root#localhost nova(keystone_admin)]# nova service-list
> +----+------------------+-----------------------+----------+---------+-------+----------------------------+-----------------+ | Id | Binary | Host | Zone | Status |
> State | Updated_at | Disabled Reason |
> +----+------------------+-----------------------+----------+---------+-------+----------------------------+-----------------+ | 6 | nova-cert | localhost.localdomain | internal | enabled |
> up | 2016-11-04T07:24:32.000000 | - | | 7 |
> nova-consoleauth | localhost.localdomain | internal | enabled | up
> | 2016-11-04T07:24:32.000000 | - | | 8 | nova-scheduler
> | localhost.localdomain | internal | enabled | up |
> 2016-11-04T07:24:33.000000 | - | | 9 | nova-conductor
> | localhost.localdomain | internal | enabled | up |
> 2016-11-04T07:24:33.000000 | - | | 11 | nova-compute
> | localhost.localdomain | nova | enabled | **down** |
> 2016-11-04T06:43:03.000000 | - | | 12 | nova-console
> | localhost.localdomain | internal | enabled | up |
> 2016-11-04T07:24:32.000000 | - |
====
[root#localhost nova(keystone_admin)]# systemctl status
openstack-nova-compute.service -l ● openstack-nova-compute.service -
OpenStack Nova Compute Server Loaded: loaded
(/usr/lib/systemd/system/openstack-nova-compute.service; enabled;
vendor preset: disabled) Active: active (running) since Fri
2016-11-04 12:08:54 IST; 49min ago Main PID: 37586 (nova-compute)
CGroup: /system.slice/openstack-nova-compute.service
└─37586 /usr/bin/python2 /usr/bin/nova-compute
Nov 04 12:08:46 localhost.localdomain systemd[1]: Starting OpenStack
Nova Compute Server... Nov 04 12:08:53 localhost.localdomain
nova-compute[37586]: Option "verbose" from group "DEFAULT" is
deprecated for removal. Its value may be silently ignored in the
future. Nov 04 12:08:53 localhost.localdomain nova-compute[37586]:
Option "notification_driver" from group "DEFAULT" is deprecated. Use
option "driver" from group "oslo_messaging_notifications". Nov 04
12:08:54 localhost.localdomain systemd[1]: Started OpenStack Nova
Compute Server.
========
The status for the nova compute process is perfectly fine.
My rabbitmq service is also running
FYI,
[root#localhost nova(keystone_admin)]# systemctl status
rabbitmq-server ● rabbitmq-server.service - RabbitMQ broker Loaded:
loaded (/usr/lib/systemd/system/rabbitmq-server.service; enabled;
vendor preset: disabled) Drop-In:
/etc/systemd/system/rabbitmq-server.service.d
└─limits.conf
Active: active (running) since Thu 2016-11-03 12:32:08 IST; 24h ago
Main PID: 1835 (beam.smp) CGroup:
/system.slice/rabbitmq-server.service
├─1835 /usr/lib64/erlang/erts-5.10.4/bin/beam.smp -W w -K true -A30 -P 1048576 -- -root /usr/lib64/erlang -progname erl -- -home
/var/lib/rabbitmq --...
├─1964 /usr/lib64/erlang/erts-5.10.4/bin/epmd -daemon
├─5873 inet_gethost 4
└─5875 inet_gethost 4
Nov 04 12:13:12 localhost.localdomain rabbitmq-server[1835]:
{user,<<"guest">>, Nov 04 12:13:12 localhost.localdomain
rabbitmq-server[1835]: [administrator], Nov 04 12:13:12
localhost.localdomain rabbitmq-server[1835]:
rabbit_auth_backend_internal,...}, Nov 04 12:13:12
localhost.localdomain rabbitmq-server[1835]: <<"/">>, Nov 04 12:13:12
localhost.localdomain rabbitmq-server[1835]: [{<<...>>,...},{...}],
Nov 04 12:13:12 localhost.localdomain rabbitmq-server[1835]:
<0.14812.0>,<0.14816.0>]}}, Nov 04 12:13:12 localhost.localdomain
rabbitmq-server[1835]: {restart_type,intrinsic}, Nov 04 12:13:12
localhost.localdomain rabbitmq-server[1835]: {shutdown,4294967295},
Nov 04 12:13:12 localhost.localdomain rabbitmq-server[1835]:
{child_type,worker}]}]}} Nov 04 12:13:12 localhost.localdomain
rabbitmq-server[1835]: function_clause
=======
[root#localhost nova(keystone_admin)]# netstat -anp | grep 5672 | grep
37586 tcp 0 0 10.1.10.22:55628 10.1.10.22:5672
ESTABLISHED 37586/python2 tcp 0 0 10.1.10.22:56204
10.1.10.22:5672 ESTABLISHED 37586/python2 tcp 0 0 10.1.10.22:56959 10.1.10.22:5672 ESTABLISHED 37586/python2
===== 37586 is the nova-compute process id.
I have checked the logs for nova-compute, nova-api and nova-conductor and there are no errors.
I have checked the nova scheduler logs and there are some errors stating refused to connect to rabbitmq and the database service.
**
2016-11-03 12:24:50.930 2092 ERROR nova.servicegroup.drivers.db
DBConnectionError: (pymysql.err.OperationalError) (2003, "Can't
connect to MySQL server on '10.1.10 .22' ([Errno 111] ECONNREFUSED)")
2016-11-03 12:24:53.811 2092 ERROR oslo.messaging._drivers.impl_rabbit
[-] AMQP server on 10.1.10.22:5672 is unreachable: [Errno 111]
ECONNREFUSED. Trying again in
**
16 seconds.
=======
Can someone suggest what should i do to handle it.
As i am on the same node, why are these services not reachable?
If nova-compute is down, there are two possible reasons:
a. nova-compute is actually down
b. it cannot communicate with rabbit, or nova-conductor cannot communicate with rabbit.
As far as I can see in your logs, you have issue with rabbit: "10.1.10.22:5672 is unreachable". Check if you have rabbit listening on this IP/port. Check if you can connect to rabbit from compute host. I usually use nc 10.1.10.22 5672 to see if there are connection or not.
Check if nova settings for rabbit are correct. Example of correct settings:
[DEFAULT]
rpc_backend=rabbit
rabbit_host=rabbitmq-ip-here
rabbit_port=5672
rabbit_hosts=$rabbit_host:$rabbit_port
rabbit_use_ssl=false
rabbit_userid=guest
rabbit_password=guest
rabbit_login_method=AMQPLAIN
rabbit_virtual_host=/compute
Check logs in the /var/log/nova/*.log
Enable debug=true in the [DEFAULT] section of nova.conf
localhost not work and IIS server stop
apache error log look like this
[Thu Jan 05 14:55:20 2012] [notice] Apache/2.2.21 (Win32) PHP/5.3.8 configured -- resuming normal operations
[Thu Jan 05 14:55:20 2012] [notice] Server built: Sep 10 2011 11:34:11
[Thu Jan 05 14:55:20 2012] [notice] Parent: Created child process 3152
[Thu Jan 05 14:55:20 2012] [notice] Child 3152: Child process is running
[Thu Jan 05 14:55:20 2012] [crit] (OS 10022)An invalid argument was supplied. : Child 3152: setup_inherited_listeners(), WSASocket failed to open the inherited socket.
[Thu Jan 05 14:55:21 2012] [crit] Parent: child process exited with status 3 -- Aborting.
[Thu Jan 05 14:55:31 2012] [notice] Apache/2.2.21 (Win32) PHP/5.3.8 configured -- resuming normal operations
[Thu Jan 05 14:55:31 2012] [notice] Server built: Sep 10 2011 11:34:11
[Thu Jan 05 14:55:31 2012] [notice] Parent: Created child process 3988
[Thu Jan 05 14:55:31 2012] [notice] Child 3988: Child process is running
[Thu Jan 05 14:55:31 2012] [crit] (OS 10022)An invalid argument was supplied. : Child 3988: setup_inherited_listeners(), WSASocket failed to open the inherited socket.
[Thu Jan 05 14:55:31 2012] [crit] Parent: child process exited with status 3 -- Aborting.
anyone know reason for this plz help for me
If you guys have still have problems with this after trying everything (like me) and the wampserver icon remains orange or some internal exception is thrown while trying to put it online, try to do following steps:
Left click the wampserver icon
Navigate to Apache->Service
Press "Remove service" and then navigate there again and press "Install service"
Restart wampserver, start/restart all services and try to put it online again
you can check out if the port 80 is open for wampserver by clicking "test port 80" inside the Apache->Service submenu
There is apparently some kind of bug or misunderstanding and wampserver didn't knew where the apache is installed
It appears to be a common issue on Win XP SP2.
"
The very simple solution is to uncheck the “Enable LMHOSTS Lookup” box in the TCP/IP protocol setup (under WINS setting). Here are the steps to do this:
Open “Control Panel” then “Network Connections.”
Right-click on “Local Area Connection” and select “Properties.”
Double-click on the “Internet Protocol (TCP/IP)” line to open the “Properties.”
On the “General” tab, click the “Advanced” button.
Select the “WINS” tab and uncheck the “Enable LMHOSTS Lookup” box.”
"
http://www.jennyconnors.com/computers/installing-apache2-and-the-wsasocket-failed-to-open-the-inherited-socket-error
I was having the same problem. It usually means that either your
C:\WINDOWS\system32\drivers\etc\hosts
C:\WINDOWS\system32\drivers\etc\lmhosts.sam
file has been changed by a program or virus.
Under Win XP SP2 or SP3, "hosts" should contain 1 entry:
127.0.0.1 localhost
lmhosts.sam should have a load of commented out statements using #.
Viruses and malware will try to put their own entries in there, so check every IP address or hostname listed. 127.0.0.1 is the local host machine, so thats cool.
i think that the problem is Related to httpd.conf file open it & change Port 80 to ex: 8081 because it could be used by another programs then try to Restart services and type http:\localhost:8081 you will find it runs
We´re using apache (2.0, with ssl) to proxy the requests to a web service installed on weblogic. We have mod_wl.so installed, and all works fine with small requests.
However, with larger requests (say, 300 KB), the apache stalls and display this error message:
"Failure of server APACHE bridge: No Backend Sever available for connections": timed out after 20 seconds or idempotent is set to off."
We replicate the scenario in another server, and the error persists (instead of "20 seconds", it says "30 seconds" for the same request).
How can I avoid this size limitation? Is it a bug in mod_wl.so? Is it a config value that is missing? (As a side note, the web service works fine when tested directly from inside the weblogic console, no matter how big the file)
Thanks for any help!
UPDATE:
changed to mod_wl_20.so with same results, here is the chunk of the log:
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[Content-Length]=[352196]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[Connection]=[Keep-Alive]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[WL-Proxy-SSL]=[true]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[WL-Proxy-Client-IP]=[163.247.57.10]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[Proxy-Client-IP]=[163.247.57.10]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[X-Forwarded-For]=[163.247.57.10]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[X-WebLogic-KeepAliveSecs]=[30]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[X-WebLogic-Request-ClusterInfo]=[true]
Wed Sep 28 11:27:37 2011 <15359131722005124> Hdrs to WLS:[x-weblogic-cluster-hash]=[2Ik836PQKnD7XHQ2RcWGOWkcRRA]
Wed Sep 28 11:27:37 2011 <15359131722005124> operation WRITE failed on fd 23: revents=0x00000018
Wed Sep 28 11:27:37 2011 <15359131722005124> IO TImed out error
Wed Sep 28 11:27:37 2011 <15359131722005124> POST timed out to the server 10.182.5.5:7005
Wed Sep 28 11:27:37 2011 <15359131722005124> ***Exception type [WRITE_ERROR_TO_SERVER] (POST ti
med out to the server 10.182.5.5:7005
) raised at line 152 of ap_proxy.cpp
Wed Sep 28 11:27:37 2011 <15359131722005124> error sending headers or Post Data to WebLogic, sys er
r#: [0] sys errmsg [Success]
Wed Sep 28 11:27:37 2011 <15359131722005124> Marking 10.182.5.5:7005 as bad
Wed Sep 28 11:27:37 2011 <15359131722005124> got exception in sendRequest phase: WRITE_ERROR_TO_SER
VER [os error=0, line 152 of ap_proxy.cpp]: POST timed out to the server 10.182.5.5:7005
at line 2994
Wed Sep 28 11:27:37 2011 <15359131722005124> Failing over after WRITE_ERROR_TO_SERVER exception in
sendRequest()
Wed Sep 28 11:27:37 2011 <15359131722005124> attempt #1 out of a max of 10
Wed Sep 28 11:27:37 2011 <15359131722005124> No good servers left in the general list, reverting ba
ck to the static list
Wed Sep 28 11:27:37 2011 <15359131722005124> Host extracted from serverlist is [10.182.5.5]
Wed Sep 28 11:27:37 2011 <15359131722005124> Host extracted from serverlist is [10.182.5.5]
Wed Sep 28 11:27:37 2011 <15359131722005124> Initializing lastIndex=0 for a list of length=2
Post timed out to 10.182.5.5:7005
This is the WebLogic which Apache is trying to post to.
You have confirmed this works when directly posted to the same Weblogic server.
The 20 seconds mathces the default KeepAliveSecs which you can try to increase.
Have you set a value in the plugin for WLIOTimeoutSecs.
This defaults to 300. Defines the amount of time in seconds the plug-in waits for a response to a request from WebLogic Server.
But from your log it does not look like Apache is waiting for 300 seconds before failing.
Similarly MaxPostSize defaults to -1, just check that you have not set some low value for that.
Check out the other plugin parameters on this list
http://download.oracle.com/docs/cd/E12840_01/wls/docs103/plugins/plugin_params.html#wp1143055
You might also want to tinker with the FileCaching element for POST requests
I have a cluster in weblogic 9.2 with 2 nodes(172.20.1.68:7101, 172.20.1.23:7102), 1 adminserver (172.20.1.23:7001) and 1 balancer (apache proxy plugin) 172.20.1.49:7103.
What I see in the balancer's access.log is that every request is marked as 404 not found. But in the node's log I can see those very same request distribuited marked as GET with code 200.
The problem is that my application is not working.
Any idea would be appreciated.
Thanks very much!
Edit:
Here it is my relevant httpd.conf, I have not section, instead I
have this:
<VirtualHost *:80>
ServerName fake.server.name
DocumentRoot "/usr/local/apache_ssl/htdocs"
<Location /myApp/>
SetHandler weblogic-handler
WebLogicCluster 172.20.1.23:7102,172.20.1.68:7101
Debug All
DebugConfigInfo ALL
WLLogFile logs/p.log
KeepAliveEnabled ON
KeepAliveSecs 15
</Location>
<Location /psoc-app>
SetHandler weblogic-handler
WebLogicCluster 172.20.1.23:7102,172.20.1.68:7101
KeepAliveEnabled ON
KeepAliveSecs 15
</Location>
WLLogFile logs/p.log
ErrorLog logs/_log_error
CustomLog logs/_log common
</VirtualHost>
/tmp/wlproxy.log request:
================New Request: [GET /myApp/path HTTP/1.1] =================
Thu Jul 29 14:30:00 2010 <1382912804066002> INFO: SSL is not configured
Thu Jul 29 14:30:00 2010 <1382912804066002> Using Uri /myApp/path
Thu Jul 29 14:30:00 2010 <1382912804066002> After trimming path: '/myApp/path'
Thu Jul 29 14:30:00 2010 <1382912804066002> The final request string is '/myApp/path'
Thu Jul 29 14:30:00 2010 <1382912804066002> SEARCHING id=[172.20.1.23:7102,172.20.1.68:7101] from current ID=[172.20.1.23:7102,172.20.1.68:7101]
Thu Jul 29 14:30:00 2010 <1382912804066002> The two ids matched
Thu Jul 29 14:30:00 2010 <1382912804066002> ###FOUND...id=[172.20.1.23:7102,172.20.1.68:7101], server_name=[172.20.1.49], server_port=[80]
Thu Jul 29 14:30:00 2010 <1382912804066002> attempt #0 out of a max of 5
Thu Jul 29 14:30:00 2010 <1382912804066002> Trying a pooled connection for '172.20.1.68/7101/7106'
Thu Jul 29 14:30:00 2010 <1382912804066002> getPooledConn: No more connections in the pool for Host[172.20.1.68] Port[7101] SecurePort[7106]
Thu Jul 29 14:30:00 2010 <1382912804066002> general list: trying connect to '172.20.1.68'/7101/7106 at line 2619 for '/myApp/path'
Thu Jul 29 14:30:00 2010 <1382912804066002> INFO: New NON-SSL URL
Thu Jul 29 14:30:00 2010 <1382912804066002> Connect returns -1, and error no set to 115, msg 'Operation now in progress'
Thu Jul 29 14:30:00 2010 <1382912804066002> EINPROGRESS in connect() - selecting
Thu Jul 29 14:30:00 2010 <1382912804066002> Local Port of the socket is 38958
Thu Jul 29 14:30:00 2010 <1382912804066002> Remote Host 172.20.1.68 Remote Port 7101
Thu Jul 29 14:30:00 2010 <1382912804066002> general list: created a new connection to '172.20.1.68'/7101 for '/myApp/path', Local port:38958
Thu Jul 29 14:30:00 2010 <1382912804066002> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 404 Not Found]
Thu Jul 29 14:30:00 2010 <1382912804066002> URL::parseHeaders: StatusLine set to [404 Not Found]
Thu Jul 29 14:30:00 2010 <1382912804066002> parsed all headers OK
Thu Jul 29 14:30:00 2010 <1382912804066002> sendResponse() : r->status = '404'
Thu Jul 29 14:30:00 2010 <1382912804066002> canRecycle: conn=1 status=404 isKA=0 clen=1214 isCTE=0
Thu Jul 29 14:30:00 2010 <1382912804066002> closeConn: URL.canRecycle() returns false, deleting URL '172.20.1.68/7101'
Thu Jul 29 14:30:00 2010 <1382912804066002> request [/myApp/path] processed sucessfully..................
Sorry I just cant get the formatter to work
From the comments so far there are 3 things to note and try:
A) Where in the Apache conf is it pointing to /tmp/wlproxy.log ? This questions whether we are looking at the right conf file - or is there perhaps another instance of Apache running?
Run this command (if on unix) to identify the owner pid writing into the log
/usr/sbin/fuser /tmp/wlproxy.log
This will return the pid of an Apache process - is that the Apache which you are running?
You could also try running fuser with your Apache shut down and see does it still show a pid owning the file?
B) The plugin debug log shows the apache request goes to the 2nd server in the cluster and gets a 404.
Thu Jul 29 14:30:00 2010 <1382912804066002> general list: created a new connection to '172.20.1.68'/7101 for '/myApp/path', Local port:38958
Thu Jul 29 14:30:00 2010 <1382912804066002> URL::parseHeaders: CompleteStatusLine set to [HTTP/1.1 404 Not Found]
Thu Jul 29 14:30:00 2010 <1382912804066002> URL::parseHeaders: StatusLine set to [404 Not Found]
Is the application definitely deployed and available on 172.20.1.68:7101/myApp/path also ?
C) What happens when you make a request for the /psoc-app shown in the conf?