I want to run 'qmlplayer' example from Qt GStreamer binder on my embedded system. My camera rtsp address uri is:
rtsp://admin:1234#192.168.2.106:554/ipcam_mjpeg.sdp
rtsp path is correct because I can run stream in VLS Player and run example with working camera view on my Ubuntu18 system. When I want run example on my embedded system I got error:
"Could not get/set settings from/on resource."
I checked in terminal:
[root#comp ~]# gst-launch-1.0 uridecodebin uri='rtsp://admin:1234#192.168.2.106:554/ipcam_mjpeg.sdp'
Setting pipeline to PAUSED ...
Pipeline is live and does not need PREROLL ...
Progress: (open) Opening Stream
Progress: (connect) Connecting to rtsp://admin:1234#192.168.2.106:554/ipcam_mjpeg.sdp
Progress: (open) Retrieving server options
Progress: (open) Retrieving media info
ERROR: from element /GstPipeline:pipeline0/GstURIDecodeBin:uridecodebin0/GstRTSPSrc:source: Could not get/set settings from/on resource.
Additional debug info:
gstrtspsrc.c(6441): gst_rtspsrc_setup_streams (): /GstPipeline:pipeline0/GstURIDecodeBin:uridecodebin0/GstRTSPSrc:source:
Could not setup transport.
ERROR: pipeline doesn't want to preroll.
Setting pipeline to PAUSED ...
Setting pipeline to READY ...
Setting pipeline to NULL ...
Freeing pipeline ...
What could be the reason? Missing linux driver? Ping is ok, iptables are droped
Related
We connected L89 GNSS module to processor via UART. I may running gpsmon and gpspipe commands on board but but not getting NMEA logs. But when we were connected L89 to processor via USB, that time I am getting NMEA logs on gpsmon and gpspipe, what is issue with UART?
I edit /etc/default/gpsd file.
# Default settings for gpsd.
# Please do not edit this file directly - use `dpkg-reconfigure gpsd' to
# change the options.
START_DAEMON="true" command to continue
GPSD_OPTIONS=""
DEVICES="/dev/ttyS1"
USBAUTO="false"
GPSD_SOCKET="/var/run/gpsd.sock"
but I am not getting NMEA data using gpsd...
Errors:
02/15 09:33:30: Launching app
$ adb push C:\Users\hp\AndroidStudioProjects\recevienotfirebase\app\build\outputs\apk\app-debug.apk /data/local/tmp/com.example.hp.recevienotfirebase
$ adb shell pm install -r "/data/local/tmp/com.example.hp.recevienotfirebase"
Success
$ adb shell am start -n "com.example.hp.recevienotfirebase/com.example.hp.recevienotfirebase.MainActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER
Client not ready yet..Connected to process 2360 on device Nexus_6P_API_24 [emulator-5554]
I/art: Not late-enabling -Xcheck:jni (already on)
W/art: Unexpected CPU variant for X86 using defaults: x86
W/System: ClassLoader referenced unknown path: /data/app/com.example.hp.recevienotfirebase-1/lib/x86
I/InstantRun: Instant Run Runtime started. Android package is com.example.hp.recevienotfirebase, real application class is null.
[ 02-15 09:33:38.693 1497: 1520 D/ ]
HostConnection::get() New Host Connection established 0x8fdb9800, tid 1520
W/System: ClassLoader referenced unknown path: /data/app/com.example.hp.recevienotfirebase-1/lib/x86
D/FirebaseApp: com.google.firebase.auth.FirebaseAuth is not linked. Skipping initialization.
W/InstanceID/Rpc: Found 10012
D/FirebaseApp: com.google.firebase.crash.FirebaseCrash is not linked. Skipping initialization.
I/FA: App measurement is starting up, version: 10084
I/FA: To enable debug logging run: adb shell setprop log.tag.FA VERBOSE
D/FA: Debug-level message logging enabled
D/FA: AppMeasurement singleton hash: 91568628
V/FA: Collection enabled
V/FA: App package, google app id: com.example.hp.recevienotfirebase, 1:1056127560632:android:663d67b615c99e63
I/FA: To enable faster debug mode event logging run:
adb shell setprop debug.firebase.analytics.app com.example.hp.recevienotfirebase
V/FA: Registered activity lifecycle callback
I/FirebaseInitProvider: FirebaseApp initialization successful
V/FA: State of service unknown
V/FA: Checking service availability
W/GooglePlayServicesUtil: Google Play services out of date. Requires 10084000 but found 9452470
D/FA: Service container out of date
V/FA: Setting useService: true
V/FA: Using measurement service
V/FA: Connecting to remote service
W/GooglePlayServicesUtil: Google Play services out of date. Requires 10084000 but found 9452470
W/art: Before Android 4.1, method android.graphics.PorterDuffColorFilter android.support.graphics.drawable.VectorDrawableCompat.updateTintFilter(android.graphics.PorterDuffColorFilter, android.content.res.ColorStateList, android.graphics.PorterDuff$Mode) would have incorrectly overridden the package-private method in android.graphics.drawable.Drawable
V/FA: onActivityCreated
V/FA: Using measurement service
V/FA: Connection attempt already in progress
V/FA: Activity resumed, time: 51631
W/gralloc_ranchu: Gralloc pipe failed
[ 02-15 09:33:52.817 2360: 2360 D/ ]
HostConnection::get() New Host Connection established 0x9e59ea40, tid 2360
W/FA: Service connection failed: ConnectionResult{statusCode=SERVICE_VERSION_UPDATE_REQUIRED, resolution=null, message=null}
I/OpenGLRenderer: Initialized EGL, version 1.4
D/OpenGLRenderer: Swap behavior 1
V/FA: Session started, time: 61634
I/FA: Tag Manager is not found and thus will not be used
D/FA: Logging event (FE): _s, Bundle[{_o=auto, _sc=MainActivity, _si=-2727167516359703917}]
V/FA: Using measurement service
V/FA: Connecting to remote service
W/GooglePlayServicesUtil: Google Play services out of date. Requires 10084000 but found 9452470
W/FA: Service connection failed: ConnectionResult{statusCode=SERVICE_VERSION_UPDATE_REQUIRED, resolution=null, message=null}
W/FA: Tasks have been queued for a long time
Google Play services out of date. Requires 10084000 but found 9452470
You may want to check this thread which states that you'll get this error when the activity is not exported. Be noted that the activity has to be exported to be accessible from adb.
Also, based from this SO post, you have to add the following to your android manifest: <action android:name="com.google.firebase.INSTANCE_ID_EVENT"/> or maybe the problem was that the onTokenRefresh() method was not called when the app was starting. Try calling FirebaseInstanceId.getInstance().getToken() in the MainActivity and see if it works.
I am new to restcomm two days ago i start following getting start guide and build restcomm from source. I am able to build successfully on my Mac machine but when i am trying to run JBoss server to run the application it is giving me some errors which i am not sure why. So my question is can i run restcomm application on MAC OS ?as mostly i see there are lot of answers are about linux OS.
MacBook-Pro:restcomm bilal$ ./start-restcomm.sh
BASEDIR: /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm
RESTCOMM_HOME: /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2
Looking for the appropriate interface
Looking for the IP Address, subnet, network and broadcast_address
Use of uninitialized value $ARGV[0] in concatenation (.) or string at /usr/local/bin/ipcalc line 136.
RestComm automatic configuration started:
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-dialogic-xms.sh...
Configuring Dialogic XMS...MS_MODE: mms
...activated Dialogic XMS...
...finished configuring Dialogic XMS!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-dialogic-xms.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-jboss-as.sh...
Configuring JBoss AS...
...disabled JBoss splash screen...
Finished configuring JBoss AS!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-jboss-as.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-load-balancer.sh...
Deactivated Load Balancer on SIP stack configuration file
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-load-balancer.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-mobicents-ms.sh...
TRUSTSTORE_FILE is not set
Configuring Mobicents Media Server... MS_ADDRESS BIND_ADDRESS NETWORK 192.168.1.0 SUBNET_MASK RTP_LOW_PORT 34534 RTP_HIGH_PORT 65535
Configured UDP Manager
Updated log configuration
Finished configuring Mobicents Media Server!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-mobicents-ms.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-restcomm.sh...
Configuring RestComm...
Updated mobicents-dar properties
Updated RestComm configuration
Configured Fax Service credentials
Configured Sms Aggregator using OUTBOUND PROXY
Configured the Speech Recognizer
Configured Acapela Speech Synthesizer
Configured VoiceRSS Speech Synthesizer
Disabled TeleStax Proxy
sed: 1: "/Users/muhammadbilal/Re ...": invalid command code m
Configured SMPP Account Details
Configured RestComm!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-restcomm.sh!
Executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-sip-connectors.sh...
Configuring Application Server...
Configured SIP Connectors and Bindings
sed: 1: "/Users/muhammadbilal/Re ...": invalid command code m
Configured gather-statistics
TRUSTSTORE_FILE is not set
Finished configuring Application Server!
Finished executing configuration file /Users/muhammadbilal/Restcomm-Connect/release/Restcomm-JBoss-AS7-7.0.2/bin/restcomm/autoconfig.d/config-sip-connectors.sh!
RestComm automatic configuration finished!
./start-restcomm.sh: line 182: ${MS_EXTERNAL^^}: bad substitution
TelScale RestComm started running on standalone mode. Screen session: restcomm.
Using IP Address:
Yes you can run Restcomm on Mac OSX, the main difference is that you need to do some more configuration manually since the auto configuration scripts don't work there as well as they do for GNU/Linux.
Please check this guide:
https://github.com/RestComm/Restcomm-Connect/wiki/Restcomm-OSX-native-installation
If you still have issues after trying such configuration, please post back here.
Best regards,
Antonis Tsakiridis
I am trying OO on a RHEL Atomic Host. I spun up OO master as a container following this guide https://docs.openshift.org/latest/getting_started/administrators.html
After attaching a shell to the Master Container, I cannot deploy an app.
# oc new-app openshift/deployment-example
error: can't look up Docker image "openshift/deployment-example": Internal error occurred: Get https://registry-1.docker.io/v2/: net/htt p: request canceled while waiting for connection error: no match for "openshift/deployment-example"
The 'oc new-app' command will match arguments to the following types:
1. Images tagged into image streams in the current project or the 'openshift' project
- if you don't specify a tag, we'll add ':latest'
2. Images in the Docker Hub, on remote registries, or on the local Docker engine
3. Templates in the current project or the 'openshift' project
4. Git repository URLs or local paths that point to Git repositories
--allow-missing-images can be used to point to an image that does not exist yet.
See 'oc new-app -h' for examples.
The host needs proxy to access Internet. I have configured proxy in /etc/sysconfig/docker and that is how I could pull the origin image in the same place.
I have tried setting proxy for master and node with luck
https://docs.openshift.org/latest/install_config/http_proxies.html
It is possible that your proxy is terminating the connection. you can test by creating an internal registry, push image to that and then use
"oc new-app your.internal.registry/openshift/deployment-example"
I am using the chrome websocket client extension to attach to a running container calling the Docker remote API like this:
ws://localhost:2375/containers/34968f0c952b/attach/ws?stream=1&stdout=1
The container is started locally from my machine executing a jar in the image that waits for user input. Basically I want to supply this input from an input field in the web browser.
Although I am able to attach using the API endpoint, I am encountering a few issues - probably due to my lackluster understanding of the ws endpoint as well as the bad documentation - that I would like to resolve:
1) When sending data using the chrome websocket client extension, the frame appears to be transmitted over the websocket according to the network inspection tool. However, the process running in the container waiting for input only receives the sent data when the websocket connection is closed - all at once. Is this standard behaviour? Intuitively you would expect that the input is immediately sent to the process.
2) If I attach to stdin and stdout at the same time, the docker deamon gets stuck waiting for stdin to attach, resulting in not being able to see any output:
[debug] attach.go:22 attach: stdin: begin
[debug] attach.go:59 attach: stdout: begin
[debug] attach.go:143 attach: waiting for job 1/2
[debug] server.go:2312 Closing buffered stdin pipe
[error] server.go:844 Error attaching websocket: use of closed network connection
I have solved this opening two separate connections for stdin and stdout, which works, but is really annoying. Any ideas on this one?
Thanks in advance!