Running Edge Server in Ubuntu
Running Edge Server in Ubuntu
Hi All,
I am running Edge Server in Ubuntu but "OSGI >" not appearing in console.
Please give me solution to resolve this problem.
using - Java7,Ubuntu 12.04
Thanks,
I am running Edge Server in Ubuntu but "OSGI >" not appearing in console.
Please give me solution to resolve this problem.
using - Java7,Ubuntu 12.04
Thanks,
- Attachments
-
- OSGI > not appearing in console.
- rifidi-osgi.JPG (73.02 KiB) Viewed 10072 times
Re: Running Edge Server in Ubuntu
Are you using rifidf 2.2 from the zip version or the deb?
Also type a command once console output stops
apps for exmaple
OSGI prompt should come up
Also type a command once console output stops
apps for exmaple
OSGI prompt should come up
Re: Running Edge Server in Ubuntu
Using rifidi 2.1 version of deb,
still OSGI prompt not showing after pressing enter and typing commands.
still OSGI prompt not showing after pressing enter and typing commands.
Re: Running Edge Server in Ubuntu
Can u post full edge server console output from point where starts to last console output
Re: Running Edge Server in Ubuntu
Installed via rifidi-edge-2.1.0-linux.gtk.x86.deb.
here is console output :
/usr/local/sbin/rifidi# ./rifidi-server
[org.eclipse.equinox.weaving.hook] info adding AspectJ hooks ...
Could not start: org.springsocial.web(reference:file:plugins/spring-social-web-1.0.2.RELEASE-osgi.jar:97). It's state is uninstalled.
START RIFIDI INITIALIZTION BUNDLE
ALL RIFIDI CONFIGURATION PATHS RELATIVE TO : /usr/local/sbin/rifidi
log4j:ERROR Could not find value for key log4j.appender.fileappender
log4j:ERROR Could not instantiate appender named "fileappender".
Using log4j configuration at: file:/usr/local/sbin/rifidi/config/logging.properties
17:52:30,954 INFO org.rifidi.edge.services.EsperManagementServiceImpl:49 - EsperManagementServiceImpl created.
17:52:31,137 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: ReadZones
17:52:31,155 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: SensorStatus
17:52:31,170 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: UniqueTagInterval
17:52:31,185 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: StableSet
17:52:31,202 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: LimitStableSet
17:52:31,210 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: UniqueTagBatchInterval
17:52:31,366 INFO com.espertech.esper.core.service.EPServiceProviderImpl:393 - Initializing engine URI 'default' version 4.7.0
17:52:32,300 ERROR org.rifidi.edge.configuration.ConfigurationServiceImpl:127 - javax.xml.bind.UnmarshalException
- with linked exception:
[java.io.FileNotFoundException: /usr/local/sbin/rifidi/config/rifidi.xml (No such file or directory)]
17:52:33,095 INFO org.springframework.remoting.rmi.RmiServiceExporter:393 - Looking for RMI registry at port '1101'
17:52:33,136 INFO org.springframework.remoting.rmi.RmiServiceExporter:404 - Could not detect RMI registry - creating new one
17:52:33,150 INFO org.springframework.remoting.rmi.RmiServiceExporter:276 - Binding service 'SensorManagerService' to RMI registry: RegistryImpl[UnicastServerRef [liveRef: [endpoint:[127.0.0.1:1101](local),objID:[0:0:0, 0]]]]
17:52:33,168 INFO org.springframework.remoting.rmi.RmiServiceExporter:393 - Looking for RMI registry at port '1101'
17:52:33,200 INFO org.springframework.remoting.rmi.RmiServiceExporter:276 - Binding service 'CommandManagerService' to RMI registry: RegistryImpl_Stub[UnicastRef [liveRef: [endpoint:[127.0.1.1:1101](remote),objID:[0:0:0, 0]]]]
17:52:33,260 INFO org.springframework.remoting.rmi.RmiServiceExporter:393 - Looking for RMI registry at port '1101'
17:52:33,266 INFO org.springframework.remoting.rmi.RmiServiceExporter:276 - Binding service 'EdgeServerManagerService' to RMI registry: RegistryImpl_Stub[UnicastRef [liveRef: [endpoint:[127.0.1.1:1101](remote),objID:[0:0:0, 0]]]]
17:52:33,333 INFO org.apache.activemq.xbean.XBeanBrokerFactory$1:500 - Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@119e0a8: startup date [Wed Sep 04 17:52:33 IST 2013]; root of context hierarchy
17:52:33,351 INFO org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader:315 - Loading XML bean definitions from file [/usr/local/sbin/rifidi/config/rifidi-amq-external.xml]
17:52:33,410 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: Tags
17:52:34,363 INFO org.apache.activemq.broker.jmx.ManagementContext:262 - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
17:52:34,380 INFO org.apache.activemq.broker.BrokerService:262 - Using Persistence Adapter: MemoryPersistenceAdapter
17:52:34,388 INFO org.apache.activemq.broker.BrokerService:262 - ActiveMQ 5.5.0 JMS Message Broker (externalBroker) is starting
17:52:34,395 INFO org.apache.activemq.broker.BrokerService:262 - For help or more information please see: http://activemq.apache.org/
17:52:35,055 INFO org.apache.activemq.transport.TransportServerThreadSupport:262 - Listening for connections at: tcp://localhost:1100
17:52:35,061 INFO org.apache.activemq.broker.TransportConnector:262 - Connector tcp://127.0.0.1:1100 Started
17:52:35,074 INFO org.apache.activemq.broker.BrokerService:262 - ActiveMQ JMS Message Broker (externalBroker, ID:prevasystems-37925-1378297354469-0:1) started
17:52:35,423 INFO org.rifidi.edge.services.ProvisioningServiceImpl:156 - Path to applications foler: /usr/local/sbin/rifidi/applications
17:52:35,837 INFO org.apache.activemq.broker.TransportConnector:262 - Connector vm://externalBroker Started
17:52:36,034 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: TagGenerator
17:52:36,079 INFO org.rifidi.edge.tools.diagnostics.TagGeneratorApp:70 - Loaded tag file with ID children
17:52:36,085 INFO org.rifidi.edge.tools.diagnostics.TagGeneratorApp:70 - Loaded tag file with ID parent
17:52:36,091 INFO org.rifidi.edge.tools.diagnostics.TagGeneratorApp:77 - Loaded Exposure properties with ID 2
17:52:36,093 INFO org.rifidi.edge.tools.diagnostics.TagGeneratorApp:77 - Loaded Exposure properties with ID 1
17:52:36,729 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: ReadZones
17:52:36,752 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: Tags
17:52:36,961 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: SensorStatus
here is console output :
/usr/local/sbin/rifidi# ./rifidi-server
[org.eclipse.equinox.weaving.hook] info adding AspectJ hooks ...
Could not start: org.springsocial.web(reference:file:plugins/spring-social-web-1.0.2.RELEASE-osgi.jar:97). It's state is uninstalled.
START RIFIDI INITIALIZTION BUNDLE
ALL RIFIDI CONFIGURATION PATHS RELATIVE TO : /usr/local/sbin/rifidi
log4j:ERROR Could not find value for key log4j.appender.fileappender
log4j:ERROR Could not instantiate appender named "fileappender".
Using log4j configuration at: file:/usr/local/sbin/rifidi/config/logging.properties
17:52:30,954 INFO org.rifidi.edge.services.EsperManagementServiceImpl:49 - EsperManagementServiceImpl created.
17:52:31,137 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: ReadZones
17:52:31,155 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: SensorStatus
17:52:31,170 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: UniqueTagInterval
17:52:31,185 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: StableSet
17:52:31,202 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: LimitStableSet
17:52:31,210 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: UniqueTagBatchInterval
17:52:31,366 INFO com.espertech.esper.core.service.EPServiceProviderImpl:393 - Initializing engine URI 'default' version 4.7.0
17:52:32,300 ERROR org.rifidi.edge.configuration.ConfigurationServiceImpl:127 - javax.xml.bind.UnmarshalException
- with linked exception:
[java.io.FileNotFoundException: /usr/local/sbin/rifidi/config/rifidi.xml (No such file or directory)]
17:52:33,095 INFO org.springframework.remoting.rmi.RmiServiceExporter:393 - Looking for RMI registry at port '1101'
17:52:33,136 INFO org.springframework.remoting.rmi.RmiServiceExporter:404 - Could not detect RMI registry - creating new one
17:52:33,150 INFO org.springframework.remoting.rmi.RmiServiceExporter:276 - Binding service 'SensorManagerService' to RMI registry: RegistryImpl[UnicastServerRef [liveRef: [endpoint:[127.0.0.1:1101](local),objID:[0:0:0, 0]]]]
17:52:33,168 INFO org.springframework.remoting.rmi.RmiServiceExporter:393 - Looking for RMI registry at port '1101'
17:52:33,200 INFO org.springframework.remoting.rmi.RmiServiceExporter:276 - Binding service 'CommandManagerService' to RMI registry: RegistryImpl_Stub[UnicastRef [liveRef: [endpoint:[127.0.1.1:1101](remote),objID:[0:0:0, 0]]]]
17:52:33,260 INFO org.springframework.remoting.rmi.RmiServiceExporter:393 - Looking for RMI registry at port '1101'
17:52:33,266 INFO org.springframework.remoting.rmi.RmiServiceExporter:276 - Binding service 'EdgeServerManagerService' to RMI registry: RegistryImpl_Stub[UnicastRef [liveRef: [endpoint:[127.0.1.1:1101](remote),objID:[0:0:0, 0]]]]
17:52:33,333 INFO org.apache.activemq.xbean.XBeanBrokerFactory$1:500 - Refreshing org.apache.activemq.xbean.XBeanBrokerFactory$1@119e0a8: startup date [Wed Sep 04 17:52:33 IST 2013]; root of context hierarchy
17:52:33,351 INFO org.apache.xbean.spring.context.v2.XBeanXmlBeanDefinitionReader:315 - Loading XML bean definitions from file [/usr/local/sbin/rifidi/config/rifidi-amq-external.xml]
17:52:33,410 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: Tags
17:52:34,363 INFO org.apache.activemq.broker.jmx.ManagementContext:262 - JMX consoles can connect to service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi
17:52:34,380 INFO org.apache.activemq.broker.BrokerService:262 - Using Persistence Adapter: MemoryPersistenceAdapter
17:52:34,388 INFO org.apache.activemq.broker.BrokerService:262 - ActiveMQ 5.5.0 JMS Message Broker (externalBroker) is starting
17:52:34,395 INFO org.apache.activemq.broker.BrokerService:262 - For help or more information please see: http://activemq.apache.org/
17:52:35,055 INFO org.apache.activemq.transport.TransportServerThreadSupport:262 - Listening for connections at: tcp://localhost:1100
17:52:35,061 INFO org.apache.activemq.broker.TransportConnector:262 - Connector tcp://127.0.0.1:1100 Started
17:52:35,074 INFO org.apache.activemq.broker.BrokerService:262 - ActiveMQ JMS Message Broker (externalBroker, ID:prevasystems-37925-1378297354469-0:1) started
17:52:35,423 INFO org.rifidi.edge.services.ProvisioningServiceImpl:156 - Path to applications foler: /usr/local/sbin/rifidi/applications
17:52:35,837 INFO org.apache.activemq.broker.TransportConnector:262 - Connector vm://externalBroker Started
17:52:36,034 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: TagGenerator
17:52:36,079 INFO org.rifidi.edge.tools.diagnostics.TagGeneratorApp:70 - Loaded tag file with ID children
17:52:36,085 INFO org.rifidi.edge.tools.diagnostics.TagGeneratorApp:70 - Loaded tag file with ID parent
17:52:36,091 INFO org.rifidi.edge.tools.diagnostics.TagGeneratorApp:77 - Loaded Exposure properties with ID 2
17:52:36,093 INFO org.rifidi.edge.tools.diagnostics.TagGeneratorApp:77 - Loaded Exposure properties with ID 1
17:52:36,729 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: ReadZones
17:52:36,752 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: Tags
17:52:36,961 INFO org.rifidi.edge.api.AbstractRifidiApp:227 - Starting App: SensorStatus
Re: Running Edge Server in Ubuntu
On Linux if you are local on the device the console will not display output when issuing commands (operates in production mode)
To issue commands you either need to telnet into the server remotely (production mode) or change the environment setting from
console 2020 # with a port (production mode only allowing command interaction remotely with sever running in background locally) - In Linux deb/zip version this is the default setting
to
console # No port number specified (Allowing local command interaction - development mode) - In windows this is default setting
Full list of how to set/use environment variables with Rifidi edge can be found here
http://wiki.rifidi.net/index.php?title= ... figuration
Extract from wiki post on using console variable
-console
This starts up the OSGi console so that you can interact with the edge server from the command line. For a list of commands that are available see Edge Server Commands. If you would like the console to be available over the network, supply a port after the -console (e.g. -console 2020). Now it is possible to telnet into the server at the given port. It is recommended that you use ssh tunneling for security reasons (i.e. first ssh to the machine that is running the edge server, then telnet to the console). One thing to note is that after you telnet to the OSGi console, you cannot use the exit command as you normally would to close the telnet session. This is because exit will be caught by the OSGi console and will perform a System.exit(). Instead, to exit the telnet session while keeping the server running, just close the telnet window.
Thx
BPP
To issue commands you either need to telnet into the server remotely (production mode) or change the environment setting from
console 2020 # with a port (production mode only allowing command interaction remotely with sever running in background locally) - In Linux deb/zip version this is the default setting
to
console # No port number specified (Allowing local command interaction - development mode) - In windows this is default setting
Full list of how to set/use environment variables with Rifidi edge can be found here
http://wiki.rifidi.net/index.php?title= ... figuration
Extract from wiki post on using console variable
-console
This starts up the OSGi console so that you can interact with the edge server from the command line. For a list of commands that are available see Edge Server Commands. If you would like the console to be available over the network, supply a port after the -console (e.g. -console 2020). Now it is possible to telnet into the server at the given port. It is recommended that you use ssh tunneling for security reasons (i.e. first ssh to the machine that is running the edge server, then telnet to the console). One thing to note is that after you telnet to the OSGi console, you cannot use the exit command as you normally would to close the telnet session. This is because exit will be caught by the OSGi console and will perform a System.exit(). Instead, to exit the telnet session while keeping the server running, just close the telnet window.
Thx
BPP
Re: Running Edge Server in Ubuntu
via telnet 2020 it works.
Thanks for ur support,
Hemanth
Thanks for ur support,
Hemanth
Re: Running Edge Server in Ubuntu
The setting "-console 2020" does not work on windows 2003/2008 server. The app runs in backgroud, but port 2020 does not accept connection. Looks like the port is not being set to listen, is there anything different that should be done in a windows server. Thank you
Re: Running Edge Server in Ubuntu
This sounds like how the windows server is operating outside of rifidi
did u do a port scan to see if anything is listening on port? (could it be possible another application that runs of windows server 2003/2008 is using port hence blocking rifidi)
bpp
did u do a port scan to see if anything is listening on port? (could it be possible another application that runs of windows server 2003/2008 is using port hence blocking rifidi)
bpp
Re: Running Edge Server in Ubuntu
I ran port scan and see several Rifidi ports but not 2020 set on config file. No other programs running on 2020 also. I tried on Win7 and same result.
Who is online
Users browsing this forum: No registered users and 4 guests