I just installed log4c and log4c-devel on CentOS 6.x by yum. All works fine except the log time, it's slow for 8 hours
Following is the output of my machine:
[rafael#localhost ~]$ date
Tue Jan 14 15:17:34 CST 2014
Following is the log produced by log4c:
20140114 07:17:34.453 DEBUG GFXLog- CTimerManager::killTimer: time id-0x0000000198c4e0.
you see, slow for 8 hours. I have setup my machine with correct time and timezone, and also keep ntpd running. I think maybe i should setup log4c timezone, but I don't know how? log4crc or code? cannot find any document about that by google.
I had exactly the same problem, but in Ubuntu 14.04 dated_local is not available because log4c is an older version. I wrote an update based on the latest log4c code which does not require modifying the supplied shared library.
See https://bugs.launchpad.net/ubuntu/+source/log4c/+bug/1314576
Related
I am finishing off a blog tutorial and am trying to do my final push to GitHub and Heroku. I just added the popper gem to the Gemfile and then tried to push to GitHub as usual using git push origin master.
Normally it then asks for my username and password, but instead I got the following error and have no idea what it means or why I got it. I haven't changed anything else as far as I remember.
fatal: unable to access 'https://github.com/<username>/FrogBlog.git/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
I am unsure how to proceed, as this message means nothing to me. I can post more files from my project if required, please advise.
GitHub recently deprecated some old and insecure cryptographic standards, including TLSv1, which is referenced in your error message:
On February 8, 2018 we’ll start disabling the following:
TLSv1/TLSv1.1: This applies to all HTTPS connections, including web, API, and git connections to https://github.com and https://api.github.com.
diffie-hellman-group1-sha1: This applies to all SSH connections to github.com
diffie-hellman-group14-sha1: This applies to all SSH connections to github.com
We’ll disable the algorithms in two stages:
February 8, 2018 19:00 UTC (11:00 am PST): Disable deprecated algorithms for one hour
February 22, 2018 19:00 UTC (11:00 am PST): Permanently disable deprecated algorithms
Most Git clients should continue to work, but there are some known incompatibilities.
If you update your Git client (it looks like you're using the standard CLI client?) pushing to GitHub will probably start working again.
I have installed Ant as i could use ant -version where it shows Apache Ant(TM) version 1.10.1 compiled on February 2 2017.i use Ubuntu 16.04 ,After I decompress voltdb,modify environment variables ,in terminal,import Ant.then the problem shows.maybe I need to illustrate I have never use it ,no data in voltdb.
I want to get it down.
the instructions for building VoltDB from source are here: https://github.com/VoltDB/voltdb/wiki/Building-VoltDB
If you can be more specific about what steps you have taken, we might be able to help. You can also contact us on our user forums, or public Slack channel.
You can also download VoltDB pre-built and try it free for 30 days.
I am trying to run a .tcl file originally configured for 2014.4 on 2016.4 version of Vivado. However I am getting the following error:
while executing
"create_bd_cell -type ip -vlnv xilinx.com:ip:mig mig_0 "
(procedure "create_root_design" line 111)
invoked from within
"create_root_design """
(file "all.tcl" line 405)
The tcl file uses the part 'xcku040-ffva1156-2' and tries to access the IP 'mig' which I believe is renamed/changed on later versions. Is there any workaround for this?
Steps I have done till now:
Changed the version number to 2016.4
tried replacing target boards.
tried on the same board with an alternate IP for mig.
tried on both 2016.4 and 2015.4 versions
None of these have worked so far
Attaching the '.tcl' file for reference : all.tcl
Since with every version upgrade of the Vivado Design Suite, parts are renamed or removed, it is not possible to run a .tcl file meant for an earlier version in newer releases. So I ran the above query on Xilinx Community Forums and found a workaround:
Run this script on the previous version(2014 in this case), generate the design and then open the same design using the next major release(2015 version). The 2015 version will automatically suggest upgrades to the discontinued/renamed IPs. Repeat the same to get to 2016 version. That's the only way to get this done. Also have to keep checking if the core functionality of the IP is the same after automated upgrades by Vivado Design Suite.
after upgrading to TFS 2017 have ceased to take place autotest issues, before everything worked fine. Can someone faced? On the Deploy TestAgent step drops. Log attached. Tried the new / old / default from the Internet TestAgent, nothing helps.Screen
Log
The error was in the Russian project name.
My local Neo4j has a lot of transaction logs in data/graph.db:
251M 3 Sep 16:44 neostore.transaction.db.0
255M 3 Sep 20:01 neostore.transaction.db.1
255M 3 Sep 23:20 neostore.transaction.db.2
251M 4 Sep 19:34 neostore.transaction.db.3
250M 4 Sep 22:16 neostore.transaction.db.4
134M 5 Sep 05:02 neostore.transaction.db.5
16B 5 Sep 09:57 neostore.transaction.db.6
16B 7 Sep 16:44 neostore.transaction.db.7
I'm backing the graph.db folder up (I have stopped the neo4j instance) in order to reload in another offsite instance, so it would be nice to reduce the folder size.
What methods are there to control these logs?
How do I check if a given neostore.transaction.db.X file has been successfully processed?
Is it safe to remove older processed files?
Logical logs are referred to in the docs, which I believe are the same files:
http://neo4j.com/docs/stable/configuration-logical-logs.html
In conf/neo4j.properties I've changed the option keep_logical_logs to 100M size:
# Keep logical logs, helps debugging but uses more disk space, enabled for
# legacy reasons To limit space needed to store historical logs use values such
# as: "7 days" or "100M size" instead of "true".
keep_logical_logs=100M size
and restarted neo4j, but it hasn't removed any of the old log files.
Can I do this manually when neo4j has stopped? Or are all of these files required?
I stopped neo4j, made a backup of the graph.db directory, removed all bar neostore.transaction.db.7 and started neo4j again. It appears to be happy but...
Thanks!
If you database in good condition you can delete all neostore.transaction.db.x files, but I recommend to you backup them.
Stop Neo4j
Delete neostore.transaction.db.x files
Start Neo4j
Updating:
In neo4j 3.x, the config has changed to:
dbms.tx_log.rotation.retention_policy=<true/false>
dbms.tx_log.rotation.retention_policy=<amount> <type>
see https://neo4j.com/docs/operations-manual/current/configuration/transaction-logs/ for more details
The properties file has a parameter for rotating TX logs:
# Will keep logical logs which contains any transaction committed within 2 days
keep_logical_logs=2 days
Check the docs for more detailed information on the different options that are available.