connmon SQLite3 errors

[Blackbat]

I'm having issues getting the develop branch of connmon running under FW 386.14_2 on my AC68u. The master branch runs fine, albeit it with scrolling problem. When I install the develop branch, however, I get a series of errors such as "connmon: SQLite3 failure: Parse error near line 3: disk I/O error (10)". Can anybody suggest how I can resolve this please?

 

[visortgw]

I'm having issues getting the develop branch of connmon running under FW 386.14_2 on my AC68u. The master branch runs fine, albeit it with scrolling problem. When I install the develop branch, however, I get a series of errors such as "connmon: SQLite3 failure: Parse error near line 3: disk I/O error (10)". Can anybody suggest how I can resolve this please?

USB drive failing?

 

[Blackbat]

USB drive failing?

It's a brand new quality USB stick, and works fine with the master branch of connmon (along with other add-ons), apart from scrolling. It's just when I install therdevelop version I see the errors.

 

[Martinski]

I'm having issues getting the develop branch of connmon running under FW 386.14_2 on my AC68u. The master branch runs fine, albeit it with scrolling problem. When I install the develop branch, however, I get a series of errors such as "connmon: SQLite3 failure: Parse error near line 3: disk I/O error (10)". Can anybody suggest how I can resolve this please?

Some context/background:
The latest 'develop' branch 3.0.3 version of connmon includes changes in the way SQLite3 errors are captured & reported in the system log. See the following post for a list of the most recent changes that were merged:

connmon - connmon - Internet connection monitoring

@Jack Yaz I checked on the code and propose the following modification to the code base. FROM (LINE 1192): if [ "$SIZEDB" -gt "$((SIZEAVAIL*1024))" ]; then TO (LINE 1192): if [ "$SIZEDB" -gt "$SIZEAVAIL" ]; then I have tried to create a dummy script to simulate this scenario (See...

www.snbforums.com

What this means is that in previous versions, any and all SQLite3 failures occurred silently and were not reported in the system log so whatever processing of database records was supposed to happen simply did not occur, and the user never knew about it.

Now, with the latest changes, the SQLite3 failures are being reported & logged, which is what you're currently seeing on your router.

The "disk I/O error (10)" errors that you see are probably caused by some type of failure on the USB-attached drive being used. IOW, the database operation could not finish because the filesystem reported an I/O error, but without further data points and context about when & where the errors occurred, it's impossible to tell exactly what the root cause may be.

 

[Blackbat]

Thanks for the comprehensive answer. I'll maybe try a different drive. It's not just the errors being logged though, connmon shows no data points with the develop branch so appears not to work at all. Maybe that's expected behaviour with the errors though.

 

[Martinski]

Thanks for the comprehensive answer. I'll maybe try a different drive. It's not just the errors being logged though, connmon shows no data points with the develop branch so appears not to work at all. Maybe that's expected behaviour with the errors though.

If you're saying that your database shows no records, it would likely mean that the I/O errors are not intermittent but consistently reported during every database operation that is attempted.

Certainly, you should try again with a different USB drive. When changing drives, make sure to disable the automatic ping tests to avoid having more errors reported in the system log while the USB drive is not available.

 

[Blackbat]

Certainly, you should try again with a different USB drive

All working now, thanks. I've bought a small branded SSD in an external enclosure and it seems to be working fine.

Edit - not working once I installed the develop version :-(

Jan 28 16:58:29 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:30 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:33 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:33 connmon: SQLite process reported error(s).
Jan 28 16:58:34 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:35 kernel: DROP IN=ppp0 OUT= MAC= SRC=103.141.137.236 DST=212.159.74.61 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=25567 PROTO=TCP SPT=52707 DPT=8609 SEQ=2210072643 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Jan 28 16:58:36 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:37 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:38 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:39 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:39 connmon: SQLite process reported error(s).

 

[Ripshod]

I don't know if this has already been asked (TL;DR) but if the release works is there a specific need to run the develop branch?

 

[Blackbat]

I don't know if this has already been asked (TL;DR) but if the release works is there a specific need to run the develop branch?

Yes there is - the scroll bar on the right of the GUI window is missing in various add-ons when using the master branch since Asuswrt-Merlin 386.14, and the dev branch for the add-ons fixes this.

 

[Martinski]

...
Edit - not working once I installed the develop version :-(

Jan 28 16:58:29 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:30 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:33 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:33 connmon: SQLite process reported error(s).
Jan 28 16:58:34 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:35 kernel: DROP IN=ppp0 OUT= MAC= SRC=103.141.137.236 DST=212.159.74.61 LEN=40 TOS=0x00 PREC=0x00 TTL=238 ID=25567 PROTO=TCP SPT=52707 DPT=8609 SEQ=2210072643 ACK=0 WINDOW=1024 RES=0x00 SYN URGP=0
Jan 28 16:58:36 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:37 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:38 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:39 connmon: SQLite3 failure: Parse error near line 5: disk I/O error (10)
Jan 28 16:58:39 connmon: SQLite process reported error(s).

When you get a chance, could you download a modified version of the latest connmon shell script using the following commands?

curl -LSs --retry 3 --retry-delay 5 --retry-connrefused \
https://raw.githubusercontent.com/jackyaz/connmon/f82cb34c5091f58bdd17c574c2a9bb30e9e26dca/connmon.sh \
-o /jffs/scripts/connmon && chmod 755 /jffs/scripts/connmon

Once downloaded, please run the following command:

/jffs/scripts/connmon outputcsv

When the above command is finished, check the system log file (/tmp/syslog.log) for the "SQLite3 failure" error messages. If you see the full set of error messages (from beginning to end), can you please post (or send me via DM) the entire log file?
Make sure to redact any sensitive information (i.e. user name, WAN IP address, etc.)

I'm hoping that the modified shell script can provide some clues about which SQLite3 command(s) is(are) reporting the errors and that might point to where & why they're being reported.

 

[Blackbat]

I'd just like to give some public thanks to @Martinski for working tirelessly with me over the last few days to resolve my connmon issue . I'm not sure what the root cause was but I assume whatever was changed will make its way into the dev branch.