ArchiveSW - Display & Data Archive Storage

downloaded the new altertables and ran. Here’s what I have.
image

Serverlog shows: “2019-12-03 19:14:27 Error running AlterTables”

1 Like

I think it might be because of a typo. Look at the extra D in the word “HubSDtatus”

1 Like

I already checked that out No Change when corrected.
image

1 Like

Geez… I fixed it. Please download again.

Sorry, Gary

1 Like

I think it’s still missing the weird, slanted, single quote looking thing in front of HubStatus. The line above has it on both ends of the word DailySky.
I can’t get my nano to copy/paste so I can’t fix it easily.

1 Like

Sorry, Still not fixed :slight_smile:

1 Like

They say, ‘Third time is the charm.’ But even I know that’s not true.

Please try, “One more time, give me just one more time.”

1 Like

do you want to update the server?
I have the same file. LOL

1 Like

It is the same file number just edits to fix my goofs.

Ok, that one seemed to work. Looked at the archive.log file and it got rid of the mqtt error but now there’s a new one:

2019-12-03 17:21:03 Error in insertHubStatus (4): ER_DATA_TOO_LONG: Data too long for column 'fs' at row 1

and it seems to be complaining about some new stuff in the altertables.log as well:

2019-12-03 17:19:47 Starting AlterTables v1.8.16.032
2019-12-03 17:19:48 Dropping table index: DailySky
2019-12-03 17:19:48 Dropping table index: PrecipEvent
2019-12-03 17:19:48 Dropping table index: SkyObservation
2019-12-03 17:19:48 Dropping table index: StrikeEvent
2019-12-03 17:19:48 Checking table index: AirBackfill
2019-12-03 17:19:48 Checking table index: AirObservation
2019-12-03 17:19:48 Checking table index: DailyAir
2019-12-03 17:19:48 Checking table index: DailySensor
2019-12-03 17:19:48 Checking table index: DailySky
2019-12-03 17:19:48 Checking table index: DeviceEvents
2019-12-03 17:19:48 Checking table index: DeviceStatus
2019-12-03 17:19:48 Checking table index: FWUpdate
2019-12-03 17:19:48 Checking table index: HubEvents
2019-12-03 17:19:48 Checking table index: HubStatus
2019-12-03 17:19:48 Checking table index: PrecipEvent
2019-12-03 17:19:48 Checking table index: RapidWind
2019-12-03 17:19:48 Checking table index: SkyBackfill
2019-12-03 17:19:49 Checking table index: SkyObservation
2019-12-03 17:19:49 Checking table index: StrikeEvent
2019-12-03 17:19:49 Checking table index: Xrain
2019-12-03 17:19:49 Checking table index: Yds18b20
2019-12-03 17:19:49 Error alterTableIndex (create index): Yds18b20 serial_number_timestamp
  ER_NO_SUCH_TABLE
2019-12-03 17:19:49 Error alterTableIndex (create index): Yds18b20 timestamp
  ER_NO_SUCH_TABLE
2019-12-03 17:19:49 Checking table index: Yuthing
2019-12-03 17:19:49 Error alterTableIndex (create index): Yuthing serial_number_timestamp
  ER_NO_SUCH_TABLE
2019-12-03 17:19:49 Error alterTableIndex (create index): Yuthing timestamp
  ER_NO_SUCH_TABLE
2019-12-03 17:19:49 Checking table index: Z_version
2019-12-03 17:19:49 Creating table: Yds18b20
2019-12-03 17:19:49 Creating table: Yuthing
2019-12-03 17:19:49 Table: HubEvents changed: fs to: varchar(10)
2019-12-03 17:19:49 Process changes complete
2019-12-03 17:19:49 Update Version complete
1 Like

Ignore those errors for now. I will find why that is wrong.

Run it again and I bet you get no errors.

1 Like

Right you are! The altertables errors went away. Just left with the
2019-12-03 17:28:43 Error in insertHubStatus (4): ER_DATA_TOO_LONG: Data too long for column 'fs' at row 1

And the Devices tab still doesn’t look quite right:

1 Like

Weird, Still getting the old file. Rebooting…
Deleted old altertables and got a fresh one.


Going out for the night. I’ll check in tomorrow. Thanks for the great support @GaryFunk !!!

1 Like

Like Gary said, try running altertables again and those errors seem to go away.
I’m heading out for dinner soon too!
Edit: here’s the results from the second running of altertables:
2019-12-03 20:51:37 Starting AlterTables v1.8.16.032
2019-12-03 20:51:38 Dropping table index: DailySky
2019-12-03 20:51:38 Dropping table index: PrecipEvent
2019-12-03 20:51:38 Dropping table index: SkyObservation
2019-12-03 20:51:38 Dropping table index: StrikeEvent
2019-12-03 20:51:38 Checking table index: AirBackfill
2019-12-03 20:51:38 Checking table index: AirObservation
2019-12-03 20:51:38 Checking table index: DailyAir
2019-12-03 20:51:38 Checking table index: DailySensor
2019-12-03 20:51:38 Checking table index: DailySky
2019-12-03 20:51:38 Checking table index: DeviceEvents
2019-12-03 20:51:38 Checking table index: DeviceStatus
2019-12-03 20:51:38 Checking table index: FWUpdate
2019-12-03 20:51:38 Checking table index: HubEvents
2019-12-03 20:51:38 Checking table index: HubStatus
2019-12-03 20:51:38 Checking table index: PrecipEvent
2019-12-03 20:51:38 Checking table index: RapidWind
2019-12-03 20:51:38 Checking table index: SkyBackfill
2019-12-03 20:51:39 Checking table index: SkyObservation
2019-12-03 20:51:39 Checking table index: StrikeEvent
2019-12-03 20:51:39 Checking table index: Xrain
2019-12-03 20:51:39 Checking table index: Yds18b20
2019-12-03 20:51:39 Checking table index: Yuthing
2019-12-03 20:51:39 Checking table index: Z_version
2019-12-03 20:51:39 Process changes complete
2019-12-03 20:51:39 Update Version complete

1 Like

Getting the same error as @todd.lorey now.


No errors on updatefiles or altertables.

1 Like

Make sure altertables is 1.8.16.032

image

Ahh, that’s a different error.

wget https://fsoft.com/archivesw/altertables.js

Here is a new file that should correct that.

I assume you meant this for me. Yes, I’m still getting the following error every 10 seconds:

2019-12-04 16:18:31 Error in insertHubStatus (4): ER_DATA_TOO_LONG: Data too long for column 'fs' at row 1
2019-12-04 16:18:41 Error in insertHubStatus (4): ER_DATA_TOO_LONG: Data too long for column 'fs' at row 1
2019-12-04 16:18:51 Error in insertHubStatus (4): ER_DATA_TOO_LONG: Data too long for column 'fs' at row 1
1 Like