I am trying to modify some APIs in MongooseIM and I want to see some logs. I tried adding lager-logging using MongooseIM, but the APIs stopped working after that.
If you have source code, you can add debug statement into it and compile it to beam file then replace the old file. The debug statement is to write some log into log file. I have used this method solving the problem in rabbitmq before.
Related
I have a non-Spring appliation. However, we are pulling in spring-security-config and spring-security-web. We use Log4j and have a log4j.properties file.
We want to log all the output from 'org.springframework' with the 'trace' log level.
We do not have an application.properties file, but can create one if we need one.
So, when I run my non-Spring app, all my code logs properyly, but I am not seeing anything from org.springframework in my logs.
Since Spring Security pulls in Spring Core, we created an application.properties on the classpath. We then setup a logging.file property to our log file. Then we setup some other logging property files to see if that would help. We also set debug=true as well.
So, I'll keep trying ....
Thanks in advance!
So, I found the problem. The logs were going to another log file in a different directory. I believe this is because it was a container log and not an application log.
Hope this helps someone else out.
I'd like to review the contents of all the debug logs on all the devices I use in my fastlane snapshot ui test?
I'm looking for the debug messages that would also be generated using NSLog etc.
I found this output_simulator_logs flag in the documentation, but it doesn't seem to work. I also set namespace_log_files but this just seems to be for the build log.
Although I'm quite happy to achieve this using another fastlane tool or maybe a different tool?
If you pass in result_bundle: true should should get some test_result bundles. In those bundles, you'll get all the logs that you're looking for. Not that *.xcactivitylog files are actually gzip'd text files.
I am trying to understand the new Parse Server and have deployed on Heroku. This went smoothly but what I am struggling with is figuring out how to write server side code (Cloud Code). I've read over the parse server example many times so I must be missing something but I'm very unclear if I should be using Express for something, or how I even begin to include my Cloud Code files. Any help is very much appreciated.
UPDATE:
I found the cloud folder I was just looking in the wrong place. I moved it and index.js to my apps folder on the desktop. I have changed the default code in main.js to my custom code. I have set up index.js with my apps information. The problem now is when I run the app and try to call the cloud code functions I get error invalid function.
If you have the parse server example running on heroku you are 90 percent there. Just open the cloud/main.js file and start adding your cloud code. There should be a hello cloud function there as an example.
To use your already created cloud code modules/files you can require them as you have done before on parse.com. The only difference is that the path should now be relative instead of absolute. For example require('cloud/cloudFunctions'); should be require('./cloudFunctions'); if you had a module called cloudFunctions.js in the cloud directory.
Cloud Code works similar to how it did on parse.com and you shouldn't have to think too much about expressjs for simple applications. That said, parse server is using expressjs so yes you are using it.
Parse server is simply a another node module similar to the other thousands available. If you do not have previous experience with nodejs, running parse server can seem complicated. Therefore I would recommend reading about the basics of nodejs before a full migration.
I'm using the Bitnami stack on a Google Compute Engine instance and I had a similar problem to yours. To solve it, just navigate to the folder where your server.js file is and create a folder called "cloud". Then create the main.js file inside the cloud folder with the following content:
Parse.Cloud.define('hello', function(req, res) {
res.success('Hi');
});
Now open the server.js file and find the line containing the path to the cloud code file. Change it to point to you main.js file like this:
This could be any arbitrary folder of your choosing.
Now just restart your parse server and call the cloud function:
String result = ParseCloud.callFunction("hello", new HashMap<>());
This is with the Java SDK but should not be much different. The variable result will equal "Hi" if you've used the function from above.
I've added dump_configuration=true to my neo4j.properties file but couldn't find the effective configuration written anywhere.
The terminal where I run bin/neo4j start from is empty and the data/log/console.log file shows that the web interface is ready but no additional prints.
Does anyone know where is it written to?
According source code of Neo4j it should be printed to stdout.
https://github.com/neo4j/neo4j/blob/4540b18f95e7eddd1cbc36c990c852962175755a/community/kernel/src/main/java/org/neo4j/unsafe/batchinsert/BatchInserterImpl.java#L1135
Anyone know where Mochiweb logs files by default? I'm running it along with the Beepbeep framework.
Mochiweb reports errors via the error_logger, so you can either write your own handler, or start SASL, and configure it to write a log file.
Aren't they kept in the priv directory next to mochiweb's start script?
Edit: Never mind, I'm wrong.
Mochiweb does not create log files as you would think it would. If you want to have apache-like logs, you'll have to roll your own.