Date   

Re: Creating Virtual Machine

IoT FDP Support
 

Hi Elsa,

Somehow, I'm not able to read your attachment(s).
Could you please post your question and or log files here: https://github.com/OSGP/Documentation/issues
This repository contains documentation for the Open Smart Grid Platform project. This repository is built as a GitBook, therefore all content has to be written using markdown syntax. See the latest GitBook: - Issues · OSGP/Documentation
github.com


Kind regards,

Kevin Smeets


From: gxf@... <gxf@...> on behalf of esantosf via lists.lfenergy.org <esantosf=gmail.com@...>
Sent: Thursday, February 17, 2022 3:01 PM
To: gxf@... <gxf@...>
Subject: [osgp] Creating Virtual Machine
 
U ontvangt niet vaak e-mail van esantosf=gmail.com@.... Meer informatie over waarom dit belangrijk is

[Edited Message Follows]

Hello
I've been having problems creating my OSGP development environment. Any help?? 
Greetings.
Elsa


Creating Virtual Machine

esantosf@...
 
Edited

Hello
I've been having problems creating my OSGP development environment. Any help?? 
Greetings.
Elsa


Re: Setting up GXF manually: Connect to localhost:443 [localhost/127.0.0.1] failed: Connection refused

BHANU SONI
 

Hi Folks,

happy new year.
In continuation of my previous work I followed Kevin's suggestion and resolved the connection error problem. Thanks, Kevin for your suggestion.
Right now I am trying decoupling the device simulator from GXF core. Running GXF core in a container and simulator in another container. The simulator container opens only ports 12123 and 12124. Device registration is successful for the simulator. But when trying to manage a device from the web demo app, the protocol adapter layer(Elster) tried to get the device status from the simulator and the connection failed due to the wrong port number. It is trying to connect to the simulator over port 12122. But the simulator doesn't have port 12122. So what configuration I am doing wrong. Can anyone please suggest?
Below changes has been done:
1. simulator container running
  - web-device-simulator.war
2. web-device-simulator.properties change:
    oslp.address.client=gxf-core >>>>> This is docker container name of gxf core(in this case 172.18.0.2)
3. Device info:
   Device Identification: SSLD_000-00-18
   Ip Address: gxf-simulator  >>>>> This is docker container name of simulator (in this case 172.18.0.4)
   Device type: SSLD
   Protocol: OSLP_ELSTER
   Firmware version: R01
   ...

Error Log:
2022-01-05 13:24:45.023] [2d5c3528f954] [protocolOslpInboundOsgpCoreRequestsMessageListenerContainer-1] INFO o.o.a.p.o.e.i.m.DeviceRequestMessageListener@onMessage:50 - Received message of type: GET_LIGHT_STATUS with message priority: 4
2022-01-05 13:24:45.024] [2d5c3528f954] [protocolOslpInboundOsgpCoreRequestsMessageListenerContainer-1] INFO o.o.a.p.o.e.i.m.p.PublicLightingGetStatusRequestMessageProcessor@processMessage:53 - Processing public lighting get status request message
2022-01-05 13:24:45.024] [2d5c3528f954] [protocolOslpInboundOsgpCoreRequestsMessageListenerContainer-1] INFO o.o.a.p.o.e.i.m.DeviceRequestMessageProcessor@printDomainInfo:69 - Calling DeviceService function: GET_LIGHT_STATUS for domain: PUBLIC_LIGHTING 1.0
2022-01-05 13:24:45.025] [2d5c3528f954] [protocolOslpInboundOsgpCoreRequestsMessageListenerContainer-1] INFO o.o.a.p.o.e.i.n.OslpDeviceService@getStatus:1279 - getStatus() for device: SSLD_000-00-18.
2022-01-05 13:24:45.026] [2d5c3528f954] [protocolOslpInboundOsgpCoreRequestsMessageListenerContainer-1] INFO o.o.a.p.o.e.a.s.o.OslpDeviceSettingsService@getDeviceByDeviceIdentification:64 - get device by device identification: SSLD_000-00-18
2022-01-05 13:24:45.029] [2d5c3528f954] [protocolOslpInboundOsgpCoreRequestsMessageListenerContainer-1] INFO o.o.a.p.o.e.i.m.SigningServerRequestMessageSender@send:45 - Sending request message to signing server, with reply-to-queue: queue://signing-server.1_0.responses-2d5c3528f954.
2022-01-05 13:24:45.034] [2d5c3528f954] [ActiveMQ Task-1] INFO o.a.a.t.failover.FailoverTransport@doReconnect:1054 - Successfully connected to tcp://localhost:61616
2022-01-05 13:24:45.061] [2d5c3528f954] [protocolOslpInboundSigningServerResponsesMessageListenerContainer-5] INFO o.o.a.p.o.e.i.m.SigningServerResponsesMessageListener@onMessage:36 - Received message of type: SIGNING_RESPONSE
2022-01-05 13:24:45.063] [2d5c3528f954] [protocolOslpInboundSigningServerResponsesMessageListenerContainer-5] INFO o.o.a.p.o.e.i.m.SigningServerResponsesMessageListener@onMessage:57 - Read signed message, messageType: SIGNING_RESPONSE, messagePriority: 4, deviceIdentification: SSLD_000-00-18, result: OK, correlationId: test-org|||SSLD_000-00-18|||20220105132444821|||1a1c43a2-46a9-4177-8ab0-9f2337c9e630
2022-01-05 13:24:45.064] [2d5c3528f954] [protocolOslpInboundSigningServerResponsesMessageListenerContainer-5] INFO o.o.a.p.o.e.a.s.o.OslpSigningService@handleSignedOslpRequest:152 - oslpEnvelope.size: 146 for message type: GET_LIGHT_STATUS
2022-01-05 13:24:45.064] [2d5c3528f954] [protocolOslpInboundSigningServerResponsesMessageListenerContainer-5] INFO o.o.a.p.o.e.i.n.OslpDeviceService@doGetStatus:1291 - doGetStatus() for device: SSLD_000-00-18.
2022-01-05 13:24:45.065] [2d5c3528f954] [protocolOslpInboundSigningServerResponsesMessageListenerContainer-5] INFO o.o.a.p.o.e.a.s.o.OslpDeviceSettingsService@getDeviceByDeviceIdentification:64 - get device by device identification: SSLD_000-00-18
2022-01-05 13:24:45.076] [2d5c3528f954] [ActiveMQ Task-1] INFO o.a.a.t.failover.FailoverTransport@doReconnect:1054 - Successfully connected to tcp://localhost:61616
2022-01-05 13:24:45.088] [2d5c3528f954] [protocolOslpInboundSigningServerResponsesMessageListenerContainer-5] INFO o.o.a.p.o.e.i.n.OslpChannelHandlerClient@send:120 - Sending OSLP request: getStatusRequest {
}

2022-01-05 13:24:45.111] [2d5c3528f954] [disposableNioEventLoopGroup-2-2] INFO i.n.handler.logging.LoggingHandler@log:148 - [id: 0xd7c8160f] REGISTERED
2022-01-05 13:24:45.112] [2d5c3528f954] [disposableNioEventLoopGroup-2-2] INFO i.n.handler.logging.LoggingHandler@log:148 - [id: 0xd7c8160f] CONNECT: /172.18.0.4:12122
2022-01-05 13:24:45.114] [2d5c3528f954] [disposableNioEventLoopGroup-2-2] INFO o.o.a.p.o.e.i.n.OslpChannelHandlerClient@operationComplete:141 - The connection to the device SSLD_000-00-18 is not successful
2022-01-05 13:24:45.115] [2d5c3528f954] [disposableNioEventLoopGroup-2-2] ERROR o.o.a.p.o.e.i.m.DeviceRequestMessageProcessor@handleUnableToConnectDeviceResponse:235 - Error while connecting to or communicating with device
org.opensmartgridplatform.shared.exceptionhandling.ConnectionFailureException: Connection failure
at org.opensmartgridplatform.adapter.protocol.oslp.elster.infra.networking.OslpDeviceService.handleException(OslpDeviceService.java:780)
at org.opensmartgridplatform.adapter.protocol.oslp.elster.infra.networking.OslpDeviceService$18.handleException(OslpDeviceService.java:1306)
at org.opensmartgridplatform.adapter.protocol.oslp.elster.infra.networking.OslpChannelHandlerClient$1.operationComplete(OslpChannelHandlerClient.java:143)
at org.opensmartgridplatform.adapter.protocol.oslp.elster.infra.networking.OslpChannelHandlerClient$1.operationComplete(OslpChannelHandlerClient.java:129)
at io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.java:577)
at io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.java:570)
at io.netty.util.concurrent.DefaultPromise.notifyListenersNow(DefaultPromise.java:549)
at io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.java:490)
at io.netty.util.concurrent.DefaultPromise.setValue0(DefaultPromise.java:615)
at io.netty.util.concurrent.DefaultPromise.setFailure0(DefaultPromise.java:608)
at io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:117)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.fulfillConnectPromise(AbstractNioChannel.java:321)
at io.netty.channel.nio.AbstractNioChannel$AbstractNioUnsafe.finishConnect(AbstractNioChannel.java:337)
at io.netty.channel.nio.NioEventLoop.processSelectedKey(NioEventLoop.java:702)
at io.netty.channel.nio.NioEventLoop.processSelectedKeysOptimized(NioEventLoop.java:650)
at io.netty.channel.nio.NioEventLoop.processSelectedKeys(NioEventLoop.java:576)
at io.netty.channel.nio.NioEventLoop.run(NioEventLoop.java:493)
at io.netty.util.concurrent.SingleThreadEventExecutor$4.run(SingleThreadEventExecutor.java:989)
at io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74)
at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
at java.lang.Thread.run(Thread.java:748)
2022-01-05 13:24:45.115] [2d5c3528f954] [disposableNioEventLoopGroup-2-2] INFO o.o.a.p.o.e.i.m.DeviceResponseMessageSender@sendMessage:55 - Sending protocol response message for device: SSLD_000-00-18 of message type: GET_LIGHT_STATUS with message priority: 4
2022-01-05 13:24:45.118] [2d5c3528f954] [ActiveMQ Task-1] INFO o.a.a.t.failover.FailoverTransport@doReconnect:1054 - Successfully connected to tcp://localhost:61616
2022-01-05 13:24:45.129] [2d5c3528f954] [disposableNioEventLoopGroup-2-2] INFO i.n.handler.logging.LoggingHandler@log:148 - [id: 0xd7c8160f] CLOSE
2022-01-05 13:24:45.130] [2d5c3528f954] [disposableNioEventLoopGroup-2-2] INFO i.n.handler.logging.LoggingHandler@log:148 - [id: 0xd7c8160f] UNREGISTERED

Regards
Bhanu Soni


On Tue, Dec 21, 2021 at 3:45 PM IoT FDP Support <IoTFDPSupport@...> wrote:
Hello Bhanu Soni,

the GXF platform uses Apache HTTPD as webserver in front of the SOAP webservice.

This repository contains the configuration for OSGP components and scripts to configure and create a development environment for the development of the OSGP platform. - Config/vhost.conf at develop...
There are server and client certificates which are used to connect to the webserver and webservice.

This repository contains the configuration for OSGP components and scripts to configure and create a development environment for the development of the OSGP platform. - Config/certificates at devel...

I have never set up GXF without the Apache HTTPD webserver. I guess it could be possible to configure the server and client certificates using only Apache Tomcat, at this moment in time I don't know how to set this up.

My suggestion would be to add Apache HTTPD, the vhost and the certificates to your environment.

Kind regards,

Kevin Smeets


From: gxf@... <gxf@...> on behalf of bhanu.soni27 via lists.lfenergy.org <bhanu.soni27=gmail.com@...>
Sent: Monday, December 20, 2021 4:09 PM
To: gxf@... <gxf@...>
Subject: [osgp] Setting up GXF manually: Connect to localhost:443 [localhost/127.0.0.1] failed: Connection refused
 
U ontvangt niet vaak e-mail van bhanu.soni27=gmail.com@.... Meer informatie over waarom dit belangrijk is
Hello dear

I am manually setting up GXF inside the docker container. I started the tomcat server through CLI(not using eclipse IDE). Everything came up good. But when clicking on add device then a redirect error came. Any help will be appiciated.

Following is an error message:
Message Request processing failed; nested exception is org.springframework.ws.client.WebServiceIOException: I/O error: Connect to localhost:443 [localhost/127.0.0.1] failed: Connection refused (Connection refused); nested exception is org.apache.http.conn.HttpHostConnectException: Connect to localhost:443 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

With Regards
Bhanu Soni


Setting up GXF manually: Connect to localhost:443 [localhost/127.0.0.1] failed: Connection refused

BHANU SONI
 

Hello dear

I am manually setting up GXF inside the docker container. I started the tomcat server through CLI(not using eclipse IDE). Everything came up good. But when clicking on add device then a redirect error came. Any help will be appiciated.

Following is an error message:
Message Request processing failed; nested exception is org.springframework.ws.client.WebServiceIOException: I/O error: Connect to localhost:443 [localhost/127.0.0.1] failed: Connection refused (Connection refused); nested exception is org.apache.http.conn.HttpHostConnectException: Connect to localhost:443 [localhost/127.0.0.1] failed: Connection refused (Connection refused)

With Regards
Bhanu Soni


Last Chance to Register | LF Energy Spring Summit is TOMORROW

Lindsay Mays Gendreau
 

Hello GXF Community,

We hope you all are doing well & having a great week!  We look forward to seeing you all tomorrow, April 14, for the LF Energy Spring Summit - Virtual!

If you have not registered yet, there are still tickets available.  REGISTER NOW - you don't want to miss this event! Check out the innovative and engaging event line-up here.

If you have questions about the Summit, please reach out to operations@... - we're happy to help!

See you tomorrow!

Arjan, Lucian, Jonas, Daniel, Shuli, John, Carly, and Lindsay
LF Energy Board & Staff


Re: Solar Energy Professionals Info

Lauren Rusen <lauren.gilbertdb@...>
 

Hi,

 

Hope my email finds you well.

 

I am just checking back to see if you had a chance to review my previous email.

 

Get access to the list mentioned below and more: -

 

  • CEOs, COOs, country managers and other management or decision makers of public and private organizations
  • Builders & Real estate Developers, Engineers, Installers and Integrators
  • Power Generation and Energy Companies, Project Developers and Planners
  • Utilities and much more…

 

Also, we can deliver other Industries as well, please specify if any.

 

Please do let me know if you have further questions regarding this and also if it is in line with your requirement.

 

Thank you for your time and consideration. Awaiting your response.

 

Best Regards,

Lauren Rusen | Inside Sales

-----------------------------------------------------------------------------------------------------------------------------------------

Hi,

 

I would like to check if you are interested in acquiring “Solar Energy Emails List” which includes complete contact details and verified email addresses across the USA, UK, Canada, Australia, Europe and most of the world.

 

Target Segments: -

  • CEOs, COOs, country managers and other management or decision makers of public and private organizations
  • Builders & Real Estate Developers, Architects, Engineers
  • Purchasing Managers, Plant Managers, Project Managers, Property Owners
  • Installers and Integrators
  • Power Generation and Energy Companies
  • Project Developers and Planners
  • Utilities
  • Architectural & Design Firm
  • Engineering firms
  • Distributors and Resellers
  • And many more…

 

Every Contact Includes with 19 data fields like: Contact Name, Company Name, Email Address, SIC Code, Phone Number, Fax Number, Website Address, Job Title, Physical Address, Revenue Size, Employee Size, Industry etc.

 

Kindly let me know your target criteria which you would like to acquire, so that I can give you more information about counts, pricing as well as a few samples for your review.

 

Target Industry: ________________??

Target Geography: ________________?? (Example: USA, UK, Canada, Australia, etc…)

Target Job Titles: ____________________?? (Example: CEO, VP’s, Directors, Managers, etc…)

 

Let me know your interest, so that we could discuss further.

 

Best Regards,

Lauren Rusen | Inside Sales

Note: If you don’t wish to receive any further emails Kindly reply with “Unsubscribe”.


APIs

Andrew Smith
 

I'm new to GXF and find the documentation too high level for my requirements, or perhaps I'm not looking in the right place.

Please point me where I can find a list of current API's .


Thank you
Andrew

1 - 7 of 7