OS X 10.10 and XCode 6.1.1.
Probably I messed up something in the project settings, as now unnecessary logs associated with AVFoundation.framework appears in the console. The first block appears while init, settings and playing music in AVPlayer.
[01:08:32.915] FigLimitedDiskCacheProvider_CopyProperty signalled err=-12784 (kFigBaseObjectError_PropertyNotFound) (no such property) at /SourceCache/CoreMedia/CoreMedia-1562.19/Prototypes/FigByteStreamPrototypes/FigLimitedDiskCacheProvider.c line 947
Jan 14 01:08:32 MacBook-Air-Roman.local rtcreporting[6668] <Info>: logging starts...
Jan 14 01:08:32 MacBook-Air-Roman.local rtcreporting[6668] <Debug>: setMessageLoggingBlock: called<
Jan 14 01:08:32 MacBook-Air-Roman.local rtcreporting[6668] <Debug>: startConfigurationWithCompletionHandler: Cached 0 enabled backends
Jan 14 01:08:32 MacBook-Air-Roman.local rtcreporting[6668] <Debug>: setUserInfoDict: enabled backends: ( )
These logs appear when I pause or play.
Jan 14 01:08:35 MacBook-Air-Roman.local rtcreporting[6668] <Debug>: sendMessageWithCategory: (null)
Jan 14 01:08:35 MacBook-Air-Roman.local rtcreporting[6668] <Debug>: sendMessageWithCategory: (null)
There's also a lot of other notices that I do not need, because all these errors are not critical, and I have never seen them before. I don't understand - how to disable this debug logs? What is it?
You can't hide them unfortunately, the best thing to do if you are analysing the logs is to paste them into notes and get rid of the rubbish by hand before analysing them.
Related
I am currently trying to get the OpenThread code lab simulation (found here) working, but unfortunately I am stuck at the chapter "Manage the network with OpenThread Daemon". All the other chapters worked like a charm, but I cannot start the daemon in the last one.
As I am completely new to this topic there might be something obvious I just don't see. Does someone know how to fix this?
OS: macOS Monterey 12.6.3
I created the daemon with ./script/cmake-build posix -DOT_DAEMON=ON and tried running it with sudo ./build/posix/src/posix/ot-daemon -v 'spinel+hdlc+forkpty:///build/simulation/examples/apps/ncp/ot-rcp?forkpty-arg=2'.
The response is always the same:
Feb 18 11:20:08 ./build/posix/src/posix/ot-daemon[9798] <Info>: Running OPENTHREAD/thread-reference-20200818-2319-gafbb2d579; POSIX; Feb 18 2023 10:39:37
Feb 18 11:20:08 ./build/posix/src/posix/ot-daemon[9798] <Info>: Thread version: 4
Feb 18 11:20:08 ./build/posix/src/posix/ot-daemon[9798] <Critical>: 49d.18:22:23.835 [C] Platform------: Init() at hdlc_interface.cpp:151: InvalidArgument
I am trying to resolve a cobbler issue, request your help/guidance on the same. we have spacewalk with cobbler. when I add a new host and do a cobbler sync, i am getting the below error and TASK FAILED.
rendering DHCP files
generating /etc/dhcp/dhcpd.conf
Exception occured: <class 'cexceptions.CX'>
Exception value: 'Error templating file, check cobbler.log for more details'
when I cross check the cobbler.log, these entries were recorded...
Mon Apr 25 14:44:45 2016 - WARNING | errors were encountered rendering the template
Mon Apr 25 14:44:45 2016 - WARNING |
[{'code': u'VFFSL(SL,"net0",True)/mac',
'exc_val': NotFound("cannot find 'net0'",),
'lineCol': (2, 11),
'rawCode': u'${net0/mac}',
'time': 'Mon Apr 25 14:44:45 2016'}]
Thanks
Nandakumar
we found its was a profile with the system Profile with a wrong name, which was stopping creating the dhcpd.conf file. After removing the particular system profile, everything works well.
Thanks
Nandakumar
With the new karma launcher for phantomJS, I am getting an annoying "Waiting 15 seconds" every time I run the tests.
The only page remotely relevant to this problem is here: https://github.com/karma-runner/karma/issues/1545
I've swapped node and karma versions a few times to try to get it to work without success. Has anyone encountered this issue?
Here's the combination of tools I'm using:
Node version: v0.10.40
karma: 0.13.15
karma-chrome-launcher: 0.2.2
karma-jasmine: 0.3.6
karma-phantomjs-launcher: 0.2.1
26 01 2016 15:06:21.897:INFO [karma]: Karma v0.13.15 server started at http://localhost:9877/karma/
26 01 2016 15:06:21.897:INFO [launcher]: Starting browser PhantomJS
26 01 2016 15:06:21.905:INFO [phantomjs.launcher]: ACTION REQUIRED:
26 01 2016 15:06:21.905:INFO [phantomjs.launcher]:
26 01 2016 15:06:21.905:INFO [phantomjs.launcher]: Launch browser at
26 01 2016 15:06:21.905:INFO [phantomjs.launcher]: http://localhost:9000/webkit/inspector/inspector.html?page=2
26 01 2016 15:06:21.905:INFO [phantomjs.launcher]:
26 01 2016 15:06:21.906:INFO [phantomjs.launcher]: Waiting 15 seconds ...
I'm using the karma-phantomjs2-launcher and you get the "waiting 15 seconds" message when debug setting is set to true. Flicking it to false got rid of the message in my case.
I would not recommend to use phantomJS. People report that its functionality can differ from Chrome or other browsers. Also you need to download it, which may fail to resume on errors.
It is more robust and reliable to use Chrome and any other real browsers you want to support. In fact, it is the main strength of Karma that you run your tests in real browsers.
Here is a minimal setup I wrote to get your started quickly, that you can also add to your current project with the single command
npm install min-karma -D
It uses Chrome but you can add any other supported browser.
It definitely will not let you wait more than a second.
I have encountered a problem with running Jboss as service on Fedora. Here is the log I have after using command: systemctl status jboss-as.service
Here is the log I have been receiving:
jboss-as.service - SYSV: JBoss AS Standalone
Loaded: loaded (/etc/rc.d/init.d/jboss-as)
Active: failed (Result: resources) since Thu 2014-01-16 09:31:54 CET; 46min ago
Process: 501 ExecStart=/etc/rc.d/init.d/jboss-as start (code=exited, status=0/SUCCESS)
Jan 16 09:31:22 servername.domain systemd[1]: Starting SYSV: JBoss AS Standalone...
Jan 16 09:31:23 servername.domain jboss-as[501]: Starting jboss-as: chown: missing operand after ‘/var/run/jboss-as’
Jan 16 09:31:23 servername.domain jboss-as[501]: Try 'chown --help' for more information.
Jan 16 09:31:54 servername.domain jboss-as[501]: [ OK ]
Jan 16 09:31:54 servername.domain systemd[1]: PID file /var/run/jboss-as/jboss-as-standalone.pid not readable (yet?) after start.
Jan 16 09:31:54 servername.domain systemd[1]: Failed to start SYSV: JBoss AS Standalone.
Jan 16 09:31:54 servername.domain systemd[1]: Unit jboss-as.service entered failed state.
First, I tried to find a solution for the chown: missin operand after ... problem and found something: here but it did not help. And also, I was looking for the answer for the PID file problem but it does not even exist in in the location: var/run/jboss-as/
This is because the startup script uses the variable $JBOSS_USER but it is not defined inside the script.
Please put in the file /etc/jboss-as/jboss-as.conf the following line:
JBOSS_USER=root
(change the root with other dedicated linux user e.g. jboss-as)
It looks like the service startup script expects to be able to write to the /var/run/jboss-as directory but doesn't have permissions to do so.
In your place I'd ensure that this directory is owned by the user that runs JBoss and that it is writable.
Check that there aren't other errors (particularly missing or incorrect paths) in your /etc/rc.d/init.d/jboss-as file (I assume you copied it from the jboss install folder to create a startup script.
I had the same issue until I fixed a completely unrelated link in that script, then it went away.
In Centos 7, if you straight way copying the jboss-as-standalone.sh in /etc/rc.d/init.d/, ensure JBOSS_CONF and JBOSS_HOME path is correct.
For me, it was with systemd. When I set the service y put wrong the PID File.
Example:
In the service was like
/var/run/jboss-as/jboss-as-standalone.pid
But in the script was like
/var/run/jboss-as/jboss-as.pid
I'm trying to open the following URL in iPad 3 Safari browser.
http://www.pearsonschool.com/index.cfm?locator=PS1yJe&PMDbProgramId=110081&sampleId=11241
And doing the following steps:
Click on "Explore the innovative technology of Teacher Place for yourself"
On the top left, click on "Dash" -> Teacher Content
Then select CMP3 Grade 7
Click on Accentuate the Negative
Then click on "3" (Multiplying and Dividing..)
Select "Problem 3.1"
Click "Launch" button
Here we have 3 options to expand viz Launch Video, Connecting to Prior or Knowledge and Presenting the Challenge.
Expand all the 3 items by clicking ">" button on right of these options.
Scroll to the bottom
It crashes.
Its working fine on iOS 5 Safari. But its crashing on iOS 6.0.1 Safari.
The following is the message that I noted during crash:
??Jan 31 07:21:13 Happiestminds kernel[0] <Debug>: 008192.238887 wlan.A[568] AppleBCMWLANNetManager::checkRealTimeTraffic(): now 8192.238881625 num entries 4
??Jan 31 07:22:07 Happiestminds ReportCrash[355] <Notice>: Formulating crash report for process MobileSafari[230]
??Jan 31 07:22:07 Happiestminds ReportCrash[355] <Error>: libMobileGestalt copySystemVersionDictionaryValue: Could not lookup ReleaseType from system version dictionary
??Jan 31 07:22:07 Happiestminds com.apple.launchd[1] (UIKitApplication:com.apple.mobilesafari[0x61fb][230]) <Warning>: (UIKitApplication:com.apple.mobilesafari[0x61fb]) Job appears to have crashed: Segmentation fault: 11
??Jan 31 07:22:07 Happiestminds backboardd[51] <Warning>: Application 'UIKitApplication:com.apple.mobilesafari[0x61fb]' exited abnormally with signal 11: Segmentation fault: 11
??Jan 31 07:22:07 Happiestminds ReportCrash[355] <Notice>: Saved crashreport to /var/mobile/Library/Logs/CrashReporter/MobileSafari_2013-01-31-072206_Happiestminds.plist using uid: 0 gid: 0, synthetic_euid: 501 egid: 0
I couldn't understand why is it crashing in latest safari.... When googled, i found that some URL's saying its problem related to Redirections, some say about bookmarking and some say about memory management. But I couldn't find the exact issue.
Can some one help me in identifying the exact issue please?
You can try to debug the javascript using chrome on mac, add console.log to your code and follow this tutorial:
http://devcoma.blogspot.it/2014/03/how-to-investigate-ios-safari-crashes.html
I've used a proxy installed on my mac in order to debug and trace from ios safari to the chrome dev tools.
I found that on my web app safari crashed when using iframes, css transitions, css overflow property and, the jQuery ready event, not all at the same time, obviously.
As and when there's updates in the browsers, we have to change the javascript etc respectively in the code as well.