Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SocNetV causes logs in syslog #23

Closed
martin3000 opened this issue Mar 8, 2017 · 12 comments
Closed

SocNetV causes logs in syslog #23

martin3000 opened this issue Mar 8, 2017 · 12 comments
Assignees
Labels
Milestone

Comments

@martin3000
Copy link

SocNetV 2.2 for Linux writes a lot of characters (megabytes) into /var/log/syslog when doing an analysis.
But I'm not sure how to reproduce it.

I find this in syslog:
Mar 8 21:43:15 mymachine compiz[2985]: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x

@oxy86
Copy link
Member

oxy86 commented Mar 8, 2017

This log excerpt is apparently from a program called "compiz", which is the compositing window manager in Ubuntu and other linux distributions, not from SocNetV. SocNetV does not use the syslog for any reason at all.
Perhaps you are experiencing a bug in Compiz with Qt5 ? What is your Linux distro/version?
This is the actual log you see? Loads of 'x' characters ?

@martin3000
Copy link
Author

This is also in syslog:

Mar 8 23:40:42 JMS-lnx compiz[2985]: MW::initSettings
Mar 8 23:40:42 JMS-lnx compiz[2985]: MW::initSettings - calling slotNetworkAvailableTextCodecs
Mar 8 23:40:42 JMS-lnx compiz[2985]: MW::initSettings - creating DialogPreviewFile object and setting codecs list
Mar 8 23:40:42 JMS-lnx compiz[2985]: MW::initSettings - creating default settings
Mar 8 23:40:42 JMS-lnx compiz[2985]: MW::initSettings - checking for settings file: "/home/jms/socnetv-data/settings.conf"
Mar 8 23:40:42 JMS-lnx compiz[2985]: MW::initSettings - settings file exist - Reading it
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "antialiasing" = "true"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "askedAboutWeights" = "false"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "considerWeights" = "false"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "dataDir" = "/home/jms/socnetv-data/"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initBackgroundColor" = "white"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initBackgroundImage" = ""
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgeArrows" = "true"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgeColor" = "black"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgeColorNegative" = "red"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgeLabelsVisibility" = "false"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgeShape" = "line"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgeThicknessPerWeight" = "true"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgeWeightNumberColor" = "#00aa00"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgeWeightNumberSize" = "7"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgeWeightNumbersVisibility" = "false"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initEdgesVisibility" = "true"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initNodeColor" = "red"
Mar 8 23:40:42 JMS-lnx compiz[2985]: read setting: "initNodeLabelColor" = "#00aa00"

@oxy86
Copy link
Member

oxy86 commented Mar 9, 2017

These are debug messages by SocNetV, indeed. SocNetV prints those messages only on startup but afterwards it stops, except when the user has selected to enable debugging.
Please open the Settings dialog (Ctrl+,) and check if the option "Print debug messages to command line" is enabled. If it is, disable it.

@martin3000
Copy link
Author

It was not enabled. I think this is openGL related. Do you use openGL in SocNetV?

@oxy86
Copy link
Member

oxy86 commented Mar 9, 2017

No, we do not use openGL. Can you please upload a more complete syslog for review?

@martin3000
Copy link
Author

I'm still researching. I deleted syslog because it was too big.
Btw: would you like to test with a .graphml file with 2500 people and 70000 connections?

@oxy86
Copy link
Member

oxy86 commented Mar 9, 2017

Yes, of course. Please send it to me (upload or email).

Which Linux version do you use ? You can check using the command

lsb_release -a

@martin3000
Copy link
Author

demo.zip

I have Ubuntu Version 16.10

@oxy86
Copy link
Member

oxy86 commented Mar 11, 2017

Hello martin3000,

the file you uploaded uses a custom schema from yworks, not the original graphml schema. This means the file has elements declared (such as <y:ShapeNode><y:NodeLabel>Unukorno</y:NodeLabel></y:ShapeNode> and <y:PolyLineEdge><y:Arrows source="none" target="none"/></y:PolyLineEdge>) which can only be read by that specific software. Nevertheless, SocNetV manages to open the file, although with various warnings/omissions (no "polylines" but labels are preserved).

I performed some analysis on your network with SocNetV, i.e. betweenness radial visualization, and I did not get any syslog messages -- as expected, SocNetV prints debug messages to syslog in Linux only if the Settings option "Print debug messages to command line" is enabled.

Thus I cannot reproduce this bug. I can only speculate that you did have the aforementioned option enabled in the first place, and then in a latter time perhaps you disabled it (?). But that would be true only if you test SocNetV again yourself with the same data and no syslog messages appear. So, can you give it another try? Delete ~/socnetv-data/settings.conf (it will be created with default settings), run SocNetV again, open the file you send me and see if any messages are printed on your syslog.

Thank you very much for your time reporting this. From the tests I realized that performance options should be added in Settings. For instance, when the loaded network has thousands edges as in your data, an option to "Disable Edge Highlighting when hovering" would be handy, since that would speed up user interactions with crowded nets.

I am attaching a zip with your network actors in radial layout according to their betweenness score. This file uses the original graphml schema.

wp-pb-betweenness-radial.graphml.zip

@oxy86 oxy86 self-assigned this Mar 11, 2017
@oxy86 oxy86 added this to the 2.3 milestone Mar 11, 2017
@oxy86 oxy86 added the bug label Mar 11, 2017
@martin3000
Copy link
Author

martin3000 commented Mar 11, 2017

I think the syslog entries are related to the big analysis tables beeing sent to chrome browser. Maybe they are not directly from your program.

@oxy86
Copy link
Member

oxy86 commented Mar 11, 2017

Does this mean that you have tested again as I suggested (having deleted the ~/socnetv-data/settings.conf to reset the app) and you saw syslog messages again? If you did, then please upload an excerpt of these to see what this is all about.

As for the analysis reports, SocNetV writes each report you execute in a HTML file inside ~/socnetv-data, and then calls the system web-browser to open that file.

@martin3000
Copy link
Author

I did not test again and I think we can close the case. As long as not other people see it...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants