As i have disconnected several time in MINT(linux) , after checking journalctl -ex i have faced "wlp4s0f0: CTRL-EVENT-BEACON-LOSS "
is there any way to fix it .
Related
The problem is simple:
When I run for example:
print(Process.runSync('ipconfig', []).stdout)
I get the expected output:
Windows IP Configuration
Unknown adapter Helyi kapcsolat:
Media State . . . . . . . . . . . : Media disconnected
Connection-specific DNS Suffix . :
......
But when I try to run ffmpeg, I get no output:
print(Process.runSync('ffmpeg', []).stdout)
What I'd expect in this case is to get the help output from ffmpeg.
My guess is, ffmpeg has some kind of "different" way of interacting with stdout than most executables. What could be the problem? I'm totally lost here.
I need to read the stdout eventually to get the output of ffmpeg -list_devices true -f dshow -i dummy, which would list the available DirectShow devices.
FFmpeg outputs useful data to stderr, including the help output and the device list of my original command, ffmpeg -list_devices true -f dshow -i dummy.
Simply use stderr (as well as stdout) to get the output:
print(Process.runSync('ffmpeg', []).stderr)
Tested in python 3.7 <=
import subprocess
s_out = subprocess.run(['ffmpeg', 'command_here'], check=True, capture_output=True).stderr
print(s_out)
"subprocess.CalledProcessError" must be returned if command is invalid.
I am running command "make px4_sitl_default gazebo" on Ubuntu18.04(VM) to work with px4 and gazebo, I install all dependencies as shown in http://docs.px4.io/master/en/simulation/gazebo.html
however, I am getting the below error every time. I didn't see anybody who takes this kinda failure all forums, so I thought somebody can help me here.
[837/841] Performing build step for 'sitl_gazebo'
ninja: fatal: invalid -j parameter
FAILED: external/Stamp/sitl_gazebo/sitl_gazebo-build
cd /home/mollaemin/PX4-Autopilot/build/px4_sitl_default/build_gazebo && /usr/bin/cmake --build /home/mollaemin/PX4-Autopilot/build/px4_sitl_default/build_gazebo -- -j 0
ninja: build stopped: subcommand failed.
Makefile:225: recipe for target 'px4_sitl_default' failed
make: *** [px4_sitl_default] Error 1
Looks like it's trying to run with -j 0 which means it is trying to do 0 consecutive jobs at once. Instead, you should manually specify how many you would like to run; i.e. make px4_sitl_default gazebo -j 4
I was trying to find a way how to build and run my game from a Ubunty-based linux container just using command line. Even though I was able to find few containers on DockerHub, neither of them allowed me to pass license registration stage in 'batch' mode.
https://hub.docker.com/r/eamonwoortman/unity3d/~/dockerfile/
https://hub.docker.com/r/chenjr0719/ubuntu-unity-novnc/
Commands I tried so far:
xvfb-run --auto-servernum /opt/Unity/Editor/Unity -force-free -batchmode -nographics -logFile -username 'xxx' -password xxx -quit
/opt/Unity/Editor/Unity -force-free -batchmode -nographics -logFile -username 'xxx' -password xxx -quit
I'm usually getting following error log from Unity:
mono profile = '/opt/Unity/Editor/Data/Mono/lib/mono/2.0' Initialize
mono Mono path[0] = '/opt/Unity/Editor/Data/Managed' Mono path[1] =
'/opt/Unity/Editor/Data/Mono/lib/mono/2.0' Mono path[2] =
'/opt/Unity/Editor/Data/UnityScript' Mono path[3] =
'/opt/Unity/Editor/Data/Mono/lib/mono/2.0' Mono config path =
'/opt/Unity/Editor/Data/Mono/etc' Using monoOptions
--debugger-agent=transport=dt_socket,embedding=1,defer=y,address=0.0.0.0:56542
DisplayProgressbar: Unity license Cancelling DisplayDialog: Failed to
activate/update license. Timeout occured while trying to update
license. Please try again later or contact support#unity3d.com This
should not be called in batch mode.
I wonder is someone else had already solved that problem and able to share Dockerfile & proper command lines.
It has been quite a while since the original question, but it took me a lot of time to find the correct answer, so just in case someone else would struggle with this problem - the answer is:
At some point Unity stopped requiring usage of xvfb-run and neatly builds stuff without it. If using xvfb-run - you'll be receiving timeouts (Unity error messages are pretty misleading in this case). I have a pipeline on Jenkins that uses Ubuntu image and these commands work fine for me so far
The trick is in using "-nographics" argument after implementation of which the need in xvfb-run disappeared.
Activate
/opt/unity/Editor/Unity -quit -logFile -batchmode -nographics -username XXXX -password XXXX -serial XXXX
Build
/opt/unity/Editor/Unity -quit -logFile -batchmode -nographics -quit -projectPath . -buildTarget iOS -customBuildTarget iOS -customBuildName XXXX -customBuildPath builds/iOS/ -executeMethod BuildCommand.PerformBuild -logFile /dev/stdout
Return license
/opt/unity/Editor/Unity -quit -logFile -batchmode -nographics -username XXXX -password XXXX -serial XXXX
Hope this saves someone that huge amount of time I wasted on figuring this out ;)
When I run opensipsctl start command for start opensips that time I got one error.
ERROR: PID file /var/run/opensips.pid does not exist -- OpenSIPS start failed
So please help me to solve it.
open up opensipsctl, it includes the file opensipsctlrc, which defined $PID_FILE as /var/run/opensips.pid
Then in opensipsctl, when you run start one of the checks is..
if [ ! -s $PID_FILE ] ; then
echo
merr "PID file $PID_FILE does not exist -- OpenSIPS start failed"
exit 1
fi
Which is saying if then check of whethever '/var/run/opensips.pid exists and is bigger than 0 bytes' fails, then echo out the above error.
This means the file isn't being created.
If you look just above that line it does..
if [ $SYSLOG = 1 ] ; then
$OSIPSBIN -P $PID_FILE $STARTOPTIONS 1>/dev/null 2>/dev/null
else
$OSIPSBIN -P $PID_FILE -E $STARTOPTIONS
fi
Which is where opensips actually starts. I would suggest adding the following to your opensips.cfg if you havn't already..
# Logging
debug=6
log_stderror=no
log_facility=LOG_LOCAL0
..now everything will be logged to /var/log/syslog on boot.
Try boot again, then look at that log for info about what's happened.
Another thing to check, is the user you're running opensips as has permission to access the directory it's trying to create the pid file in.
I had the same error & it was driving me mad as well. I managed to trace it down to one of two things - I had both!
1/ A misconfiguration in the OpenSIPS config file. journalctl -xe should be able to tell you what the error is
2/ Something else is listening on the port that you are trying to listen on
For 2, you can try the below, if you have Ubuntu, to see if anything is already listening on that port
lsof -i :5060
I was able to see logs and fix issue by below steps
Set log_level=4 in opensips.cfg to view debug logs in /var/log/syslog
debug is deprecated in 2.4 and higher version.
You can refer here for different log level
I am trying to upload hello-world in Micaz using Contiki.
I followed these steps
user#instant-contiki:~$ cd contiki/examples/hello-world
user#instant-contiki:~/contiki/examples/hello-world$ make TARGET=micaz hello-world
CC hello-world.c
LD hello-world.micaz
rm hello-world.co
user#instant-contiki:~/contiki/examples/hello-world$ make TARGET=micaz savetarget
saving Makefile.target
Finally while uploading I got the below error
user#instant-contiki:~/contiki/examples/hello-world$ make hello-world.upload
using saved target 'micaz'
avr-objcopy -O srec hello-world.micaz hello-world.srec
uisp -dprog=mib510 -dserial=/dev/ttyS0 -dpart=ATmega128 --wr_fuse_h=0xd1 --wr_fuse_e=ff --erase --upload if=hello-world.srec --verify
Error: Permission denied
-> /dev/ttyS0
make: *** [hello-world.upload] Error 1
rm hello-world.srec
I have seen many Stackoverflow questions regarding the same .
But those workaround is not solving my issues.
Am I doing anything wrong.
Please Suggest.
First of all, the problem is about permission.
Try "sudo make hello-world.upload"
And if you use Instant contiki 2.7 and it is your first time compiling with Micaz,
you may have another problem about "make: uisp: Command not found"
Then, refer following link.
http://iotnet.blogspot.kr/2014/07/contiki-micaz-2-uisp-command-not-found.html