[Dxspider-support] ipaddr is null in mysql DB
Dirk Koopman
djk at tobit.co.uk
Sat Jun 6 18:20:31 CEST 2020
There is at least one DXSpider instance which sees 1000+ users and 30
odd nodes most weekends now running in Digital Oceans smallest $5 droplet.
I though I would just check that the mysql spot insertion still works so
I installed the version of MariaDB that comes with Ubuntu 18.04 and
(after I got the permissions right) this happens:
MariaDB [dxspider]> select * from spot;
+-------+---------+--------------+------------+---------------------------------+---------+----------+-------------+----------+---------+--------+------------+-----------+-----------+--------------+-----------------+
| rowid | freq | spotcall | time |
comment | spotter | spotdxcc | spotterdxcc |
origin | spotitu | spotcq | spotteritu | spottercq | spotstate |
spotterstate | ipaddr |
+-------+---------+--------------+------------+---------------------------------+---------+----------+-------------+----------+---------+--------+------------+-----------+-----------+--------------+-----------------+
| 1 | 14294 | W2I/STAYHOME | 1591459020 | CQ
CQ | PB5X | 226 | 139 |
WA9PIE-2 | 8 | 5 | 27 | 14 | NULL |
NULL | 84.104.178.54 |
| 2 | 14260 | KY4X | 1591459020 |
NULL | K4NAU | 226 | 226 | AE5E
| 8 | 4 | 8 | 4 | KY | SC |
45.16.255.32 |
| 3 | 21027.4 | 4U1UN | 1591459020 | No copy
2el,KN10 | SV2EVS | 284 | 156 | SV2HRT-1
| 8 | 5 | 28 | 20 | NULL | NULL |
37.6.159.17 |
| 4 | 28074 | KG5ABO | 1591459020 | FT-8,
Texas | VE3PV | 226 | 197 | VK3AMA-2
| 7 | 4 | 4 | 4 | TX | NULL |
108.160.156.103 |
| 5 | 14042.8 | WB2UBW/SIM | 1591459020 |
CW | W3RZ | 151 | 226 | K5DX
| 18 | 14 | 8 | 5 | NULL | PA |
NULL |
| 6 | 14018.1 | PR7AB | 1591459020 |
CW | PP1CZ | 142 | 142 | VE7CC-1
| 13 | 11 | 15 | 11 | NULL | NULL |
181.213.78.201 |
| 7 | 14248 | ND4X | 1591459020 | KY QP cq
cq | MI0SAI | 226 | 63 | N0VD-7
| 8 | 4 | 27 | 14 | KY | NULL |
NULL |
| 8 | 7112 | IZ4AFM | 1591459020 | San
Miguel | EA1BQR | 85 | 34 |
EA4URE-2 | 28 | 15 | 37 | 14 | NULL |
NULL | 192.168.1.110 |
| 9 | 70154 | G0WUU | 1591459020 | KO02LI<ES>IO92 FT8 -14dB
Tnx | SP5AOZ | 61 | 152 | EA6VQ-1 | 27 | 14
| 28 | 15 | NULL | NULL | NULL |
| 10 | 21027.4 | 4U1UN | 1591459020 |
NIL | F8CRS | 284 | 42 | SR2PUT
| 8 | 5 | 27 | 14 | NULL | NULL |
84.17.52.174 |
| 11 | 144308 | F5RNN | 1591459020 | <JN25JH> dept 26 tnx
Jean paul | F0FGF | 42 | 42 | OK2CQR-1 | 27 |
14 | 27 | 14 | NULL | NULL | 94.23.250.107 |
| 12 | 14210 | OH6STAYHOME | 1591459080 | strong in
uk | 2E0GLN | 130 | 61 | HA6DX
| 18 | 15 | 27 | 14 | NULL | NULL |
NULL |
| 13 | 7071 | EA3IIH | 1591459080 | dipl.dia mundial medio
ambiente | EA3IAZ | 34 | 34 | WA9PIE-2 | 37 |
14 | 37 | 14 | NULL | NULL | 147.161.123.183 |
+-------+---------+--------------+------------+---------------------------------+---------+----------+-------------+----------+---------+--------+------------+-----------+-----------+--------------+-----------------+
Now, I did find a small issue with the code but that only affected
reading the database, not inserting new spots.
Please could you check that you are getting PC61 spots as well as PC11.
Only the PC61 spots contain the IP addresses, e.g:
<- I GB7DJK PC11^14188.0^4S7JL/MM^6-Jun-2020^1615Z^now CQ By numbers
!!^MI0SAI^N0VD-7^H98^~
<- I GB7DJK PC61^50313.00^OH7KM^06-Jun-2020^1615Z^FT8 -7 +269hz KP11 CQ
DX^WW1L^VE7CC-1^67.255.65.68^H95^~
<- I GB7DJK PC61^50313.00^OH3SR^06-Jun-2020^1615Z^FT8 -13 +1789hz
KP21^WW1L^VE7CC-1^67.255.65.68^H95^~
If you want a reliable source of PC61 then you can connect to
gb7djk.dxcluster.net 7300 and get them there. I have set you up on -2
and -3 as a node.
Dirk G1TLH
On 05/06/2020 22:55, JMarcio S via Dxspider-support wrote:
>
> Hi Dirk,
>
> Thanks for info, I consider the dx spider a very good
> application and now with a lot of quick search options in the 'mojo
> 1.57' sh/dx is fast, very good job, thank you!
>
> I'm running on a VM (Digital Ocean), with very little RAM and CPU used.
>
> I am not running dxspider on older versions. Currently, I have two
> nodes in the VM, the first version is: 155, build 0.204 and the second
> virtual machine is: 1.57 build 252 (mojo).
>
> To populate the MySQL database, I configure DXVARS, I don't write code
> for this, only dxspider package.
>
> # the SQL database DBI dsn
>
> $dsn = "dbi:mysql:dxcluster:xxx.xxx.xxx.xx:yyyy”;
>
> $dbuser = “xxxxx”;
>
> $dbpass = “xxxxxxx”x;
>
> and then the process is automatic, the DB is populated with the fields
> (freq, spotcall, time, comment, spotter, spotdxcc.spotterdxcc, origin,
> itu, cq, usstate, and ipaddr).
>
> all of these fields are loaded normally when using node version 155,
> build 0.204
>
> when using node version 1.57 build 252 the ipaddr field is not loaded.
> I thought it had something to do with the new version of DXspider.
>
> I'm not sure if I found the right information. I started 'watchdbg'
> and the result was:
>
> version 1.57/252
>
> 09:34:23 (chan) <- I PY4OG-2
> PC92^DH1TW-2^34462^A^^7K1TTT-1:208.125.133.190^H93^
>
> 09:34:23 (chan) <- I PY4OG-2
> PC92^IW1QLH-6^34462^A^^7JG1VGX-8:3.115.254.10^H94^
>
> 09:34:46 (chan) <- I PY4OG-2 PC11^70154.0^OK2BRD^ 5-Jun-2020^0934Z^<ES>
>
> version 155/0204
>
> 09:40:24 -> D PY4OG-4 PC92^F4BWT-3^34824^D^^5F6BVP-3^H93^
>
> 09:40:24 -> D PY3NZ-8 PC92^F4BWT-3^34824^D^^5F6BVP-3^H93^
>
> 09:40:24 <- I WB3FFV-2 PC41^IW2CLM^1^Dome^H29^~
>
> Mysql DB is only for queries on a rest API created to connect
> with mobile devices, you can see the results accessing the iDX App
> only for iOS devices. This database was the way found to develop this
> interface is also to add new information to the spot line, such as
> dxpeditions, lotw, special events, beacons and other filters in real
> time. I cannot say if it is a faster solution, but it is imperceptible.
>
> To send spots I use Telnet tcp/socket via standard dxspider, ipaddr is
> correct.
>
> No problem, currently I don't use the ip filter in mysql just in
> DxSpider and there, everything works fine. I just thought of helping
> to fix any bug in the 'mojo' version, but everything is understood
> now. Well, I will now try a new installation and replace the necessary
> DBI drivers for the mysql interface.
>
> thank you again
>
> 73 J.Marcio PY4OG
>
>
> Em qua., 3 de jun. de 2020 às 09:10, Dirk Koopman via Dxspider-support
> <dxspider-support at tobit.co.uk <mailto:dxspider-support at tobit.co.uk>>
> escreveu:
>
> I don't know why that should be. At this point I need to write the
> programmer's lament: "I never touched that bit of the code".
>
> My changes are just concerned with searching, not spot storage.
>
> Are you getting PC61 style spots? Are they mainly first or not?
> This last question is because I store the first version of a spot
> that comes in. There are still (too many) old DXSpider nodes out
> there that do not generate PC61 instead of PC11 (and the less said
> about DXSummit the better).
>
> It would be interesting to compare the output of this:
>
> grepdbg 'I [-\w]+ PC[61]1'
>
> to a SQL query.
>
> I WISH SYSOPs WOULD UPDATE THEIR SOFTWARE TO THE LATEST VERSION ON
> THEIR BRANCH. The mojo branch is a bit experimental, particularly
> as I am stuck at home not doing very much. But if you on the
> standard 'master' branch, you should update your software at least
> every couple of months. It gets you some fixes that the mojo
> branch work has found and also updated prefix information. The
> fact that there are so many PC11 spots still being generated means
> that your _node has not been updated since at least 2012_!
>
> Back to the point:
>
> This is the entire code that stores a spot. @_ contains the
> expanded spot data (the spot + all the country, zone and US state
> data) in separate fields.
>
> sub add
> {
> my $buf = join('^', @_);
> $fp->writeunix($_[2], $buf);
> if ($main::dbh) {
> $main::dbh->begin_work;
> $main::dbh->spot_insert(\@_);
> $main::dbh->commit;
> }
> $totalspots++;
> if ($_[0] <= 30000) {
> $hfspots++;
> } else {
> $vhfspots++;
> }
> if ($_[3] =~ /(?:QSL|VIA)/i) {
> my $q = QSL::get($_[1]) || new QSL $_[1];
> $q->update($_[3], $_[2], $_[4]);
> }
> }
>
> Now, I am afraid that I don't run a MySQL database and am not
> generally a fan because it has a nasty tendency to take every
> spare piece of RAM that it can find - although that behaviour may
> now have changed in the 8 years or so since I last looked at this.
>
> 73 Dirk G1TLH
>
> On 03/06/2020 02:43, JMarcio S via Dxspider-support wrote:
>> Hi Dirk
>> The ipaddr in the Mysql database is null, after Mojo. Any
>> format changes? current is: VARCHAR 40. (running DXSpider V1.57
>> build 252).
>> Thank you again
>>
>> J.Marcio PY4OG
>>
>> _______________________________________________
>> Dxspider-support mailing list
>> Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
>> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk <mailto:Dxspider-support at tobit.co.uk>
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
>
>
>
> --
> J.Marcio
>
> _______________________________________________
> Dxspider-support mailing list
> Dxspider-support at tobit.co.uk
> https://mailman.tobit.co.uk/mailman/listinfo/dxspider-support
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20200606/e9480697/attachment-0001.htm>
More information about the Dxspider-support
mailing list