Comments (6)
jelu
commented on August 18, 2024
I can help when I'm back working on Monday.
Until then, have you:
- checked that the XMLs contain data on your CentOS7?
- that they are transfered correct to your debian 10?
- and that they are processed so that the DAT files contain data?
from dsp.
jelu
commented on August 18, 2024
So, have you checked the above things?
from dsp.
armaneth95
commented on August 18, 2024
Hi @jelu ,
Thanks for your quick answer. Sorry for being late to answer.
As the preview of this message is not showing well I attached a file containing all of the outputs through this link https://www.dropbox.com/s/rja3mjxbydv4tco/Output_DSP.txt?dl=0
- checked that the XMLs contain data on your CentOS7?
In my DSP config, $SERVER = debian and $NODE = dns01
Here is the containt an XML file generated and sent to the DSP on 2021-06-07. The following command is executed on the DSP (Debian10)
cat /var/lib/dsc/debian/dns01/done/20210617/dscdata/1623955500.dscdata.xml
<dscdata>
<array name="pcap_stats" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="ifname"/>
<dimension number="2" type="pcap_stat"/>
<data>
<ifname val="ens33">
<pcap_stat val="pkts_captured" count="56"/>
<pcap_stat val="filter_received" count="56"/>
</ifname>
</data>
</array>
<array name="direction_vs_ipproto" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="Direction"/>
<dimension number="2" type="IPProto"/>
<data>
</data>
</array>
<array name="client_port_range" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="PortRange"/>
<data>
</data>
</array>
<array name="transport_vs_qtype" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="Transport"/>
<dimension number="2" type="Qtype"/>
<data>
</data>
</array>
<array name="ipv6_rsn_abusers" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="ClientAddr"/>
<data>
</data>
</array>
<array name="idn_vs_tld" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="TLD"/>
<data>
</data>
</array>
<array name="rd_bit" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="RD"/>
<data>
</data>
</array>
<array name="do_bit" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="D0"/>
<data>
</data>
</array>
<array name="edns_bufsiz" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="EDNSBufSiz"/>
<data>
</data>
</array>
<array name="edns_version" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="EDNSVersion"/>
<data>
</data>
</array>
<array name="idn_qname" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="IDNQname"/>
<data>
</data>
</array>
<array name="chaos_types_and_names" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="Qtype"/>
<dimension number="2" type="Qname"/>
<data>
</data>
</array>
<array name="client_addr_vs_rcode" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="Rcode"/>
<dimension number="2" type="ClientAddr"/>
<data>
</data>
</array>
<array name="client_subnet2" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="Class"/>
<dimension number="2" type="ClientSubnet"/>
<data>
</data>
</array>
<array name="certain_qnames_vs_qtype" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="CertainQnames"/>
<dimension number="2" type="Qtype"/>
<data>
</data>
</array>
<array name="qtype_vs_tld" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="Qtype"/>
<dimension number="2" type="TLD"/>
<data>
</data>
</array>
<array name="qtype_vs_qnamelen" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="Qtype"/>
<dimension number="2" type="QnameLen"/>
<data>
</data>
</array>
<array name="client_subnet" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="ClientSubnet"/>
<data>
</data>
</array>
<array name="rcode_vs_replylen" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="Rcode"/>
<dimension number="2" type="ReplyLen"/>
<data>
</data>
</array>
<array name="opcode" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="Opcode"/>
<data>
</data>
</array>
<array name="rcode" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="Rcode"/>
<data>
</data>
</array>
<array name="qtype" dimensions="2" start_time="1623955440" stop_time="1623955500">
<dimension number="1" type="All"/>
<dimension number="2" type="Qtype"/>
<data>
</data>
</array>
</dscdata>
- that they are transfered correct to your debian 10?
As you can see below, the scripts are working fine and every 60s at get new XML uploaded to the DSP
root@debian:~# ls -l /var/lib/dsc/debian/dns01/incoming/2021-06-21/
total 8
-rw-rw-r-- 1 root root 4536 juin 21 10:08 1624266480.dscdata.xml
root@debian:~# date +%s
1624266523
- and that they are processed so that the DAT files contain data?
Here are the .dat generated on 2021-06-17
root@debian:~# ls -l /var/lib/dsc/debian/dns01/20210617/
total 268
-rw-r--r-- 1 root root 525 juin 17 20:18 certain_qnames_vs_qtype.dat
-rw-r--r-- 1 root root 49 juin 17 20:18 chaos_types_and_names.dat
-rw-r--r-- 1 root root 98 juin 17 20:18 client_addr_vs_rcode_accum.dat
-rw-r--r-- 1 root root 16575 juin 17 20:18 client_port_range.dat
-rw-r--r-- 1 root root 141 juin 17 20:18 client_subnet2_accum.dat
-rw-r--r-- 1 root root 410 juin 17 20:18 client_subnet2_count.dat
-rw-r--r-- 1 root root 436 juin 17 20:18 client_subnet2_trace.dat
-rw-r--r-- 1 root root 56 juin 17 20:18 client_subnet_accum.dat
-rw-r--r-- 1 root root 13179 juin 17 20:18 client_subnet_count.dat
-rw-r--r-- 1 root root 734 juin 17 20:18 direction_vs_ipproto.dat
-rw-r--r-- 1 root root 11340 juin 17 20:18 dnssec_qtype.dat
-rw-r--r-- 1 root root 11315 juin 17 20:18 do_bit.dat
-rw-r--r-- 1 root root 11368 juin 17 20:18 edns_bufsiz.dat
-rw-r--r-- 1 root root 11329 juin 17 20:18 edns_version.dat
-rw-r--r-- 1 root root 11375 juin 17 20:18 idn_qname.dat
-rw-r--r-- 1 root root 0 juin 17 20:18 idn_vs_tld.dat
-rw-r--r-- 1 root root 0 juin 17 20:18 ipv6_rsn_abusers_accum.dat
-rw-r--r-- 1 root root 13179 juin 17 20:18 ipv6_rsn_abusers_count.dat
-rw-r--r-- 1 root root 11275 juin 17 20:18 opcode.dat
-rw-r--r-- 1 root root 59529 juin 17 20:18 pcap_stats.dat
-rw-r--r-- 1 root root 11325 juin 17 20:18 qtype.dat
-rw-r--r-- 1 root root 350 juin 17 20:18 qtype_vs_qnamelen.dat
-rw-r--r-- 1 root root 564 juin 17 20:18 qtype_vs_tld.dat
-rw-r--r-- 1 root root 11254 juin 17 20:18 rcode.dat
-rw-r--r-- 1 root root 595 juin 17 20:18 rcode_vs_replylen.dat
-rw-r--r-- 1 root root 11315 juin 17 20:18 rd_bit.dat
-rw-r--r-- 1 root root 531 juin 17 20:18 transport_vs_qtype.dat
root@debian:~# cat /var/lib/dsc/debian/dns01/20210617/transport_vs_qtype.dat
1623892620 udp 1:169
1623892680 udp 1:1:28:1
1623893040 udp 1:1:28:1
1623893160 udp 28:1:1:1
1623893400 udp 12:1
1623893520 udp 1:169
1623893580 udp 1:338
1623893640 udp 1:338
1623893700 udp 1:339
1623893760 udp 1:172:28:3
1623893820 udp 28:4:1:84
1623893880 udp 1:192
1623893940 udp 1:130
1623894000 udp 1:192
1623894060 udp 1:146
1623894120 udp 28:5:1:174
1623894240 udp 28:1:1:170
1623895500 udp 2:1:else:1 tcp 2:1:else:1
1623920100 udp 12:1
1623921900 udp 28:5:1:9 tcp 28:5:1:9
1623957420
#MD5 185952c5e85d275befd43fa636fc30e1
root@debian:~# cat /var/lib/dsc/debian/dns01/20210617/qtype.dat
root@debian:~# cat /var/lib/dsc/debian/dns01/20210617/qtype_vs_tld.dat
tr 1 31
io 1 15
gr 1 16
145 28 2
145 1 2
tw 1 14
il 1 15
ro 1 63
nl 1 60
es 1 15
iq 1 16
be 1 31
. 2 2
fi 1 16
pl 1 15
dk 1 16
bg 1 30
sg 1 16
hk 1 16
com 1 551
com 28 12
org 28 3
org 1 145
net 28 4
net 1 329
hu 1 46
by 1 15
se 1 47
si 1 16
cn 1 61
de 1 184
cz 1 46
jp 1 48
id 1 15
rs 1 15
sk 28 3
sk 1 3
it 1 15
fr 1 32
info 1 16
edu 1 134
at 1 47
ua 1 30
lv 1 16
is 1 31
br 28 1
br 1 1
za 28 1
za 1 17
ru 1 30
pt 1 47
arpa 12 2
nz 1 31
ec 1 30
kz 1 30
az 1 15
ge 1 16
ch 1 16
ee 1 16
ma 1 16
md 1 16
ca 1 30
uk 1 48
au 1 46
#MD5 d08799af77bffc46d5e1578450ed3f82
root@debian:~#
Thanks for your help
from dsp.
jelu
commented on August 18, 2024
Do you have ploticus installed on debian?
Have you checked your webservers error log?
from dsp.
armaneth95
commented on August 18, 2024
Looks like ploticus is installed
root@debian:~# dpkg -l | grep ploticus
ii ploticus 2.42-4 amd64 script driven business graphics package
root@debian:~#
Here is the output of the NGINX error log
root@debian:~# tail /var/log/nginx/error.log
2021/06/21 10:42:57 [error] 448#448: *1 FastCGI sent in stderr: "pl: error 12014: Cannot open for write (/var/cache/dsp/edefcbc4af7e3839a8f2c123920ed4c3.png.new)" while reading response header from upstream, client: 172.16.194.1, server: _, request: "GET /dsc-grapher.pl?node=dns01&server=debian&plot=transport_vs_qtype HTTP/1.1", upstream: "fastcgi://unix:/var/run/fcgiwrap.socket:", host: "172.16.194.145", referrer: "http://172.16.194.145/dsc-grapher.pl?server=debian&node=dns01&plot=bynode"
Now i get it.
/var/cache/dsp/ didn't exist. So I created it and make www-data owner.
Now the graphs are available.
I still remain intrigued because on the DSP I've configured on Ubuntu 18.04 I ddn't created this directory but I does exist and is owned by www-data.
Thanks a lot @jelu for your help
from dsp.
jelu
commented on August 18, 2024
You must have created it for Ubuntu, there is nothing else that do that. It's in the wiki also, so maybe you just missed it for Debian.
from dsp.
Related Issues (8)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from dsp.