openLuup email server

[akbooer]

@catmanv2 said in Logging lines:

I hate to labour the point, but that fix that I tried?

Oh, yes, right you are. I seem to have lost the plot completely.

...but looking again at the original thread, I see:

@akbooer said in Logging and rotation:

All you need is a one-liner in the Lua Startup Code.

but you responded

OK, so reading the doc I've done this:

luup.attr_set ("openLuup.Logfile.Lines", 20000)

But I assume that's not going to persist.

Do I just do

attr ("openLuup.Logfile.Lines", "20000")

In the start up Lua window?

..and, in fact, I never followed up on that.

So I've just re-tried my original instruction, to add a one-line in the Startup Code (and save it, and reload.)

luup.attr_set ("openLuup.Logfile.Lines", 20000)

which does what I (and you) expect.

...so it was working all the time...

[CatmanV2]

@akbooer said in Logging lines:

OK giving that a try

C

[CatmanV2]

Ummm

So I put this in my Startup code window

-- Add the log lines
local attr = luup.attr_set ("openLuup.Logfile.Lines", 20000)

Submitted, I assumed it reloaded? It already rotated at 2000 lines. I've forced another reload and am just waiting....

C

[akbooer]

Check that the startup line is still there.

[akbooer]

Actually, the line that I recommended is:

luup.attr_set ("openLuup.Logfile.Lines", 20000)

[CatmanV2]

Apologies. I'll try that. My version didn't work

C

[akbooer]

Note that you do have to do an explicit Luup reload after saving the Startup Lua... unlike Vera, it does not force an automatic reload (thus allowing you to make other changes before reloading.)

[CatmanV2]

@akbooer said in Logging lines:

Note that you do have to do an explicit Luup reload after saving the Startup Lua... unlike Vera, it does not force an automatic reload (thus allowing you to make other changes before reloading.)

Cheers. It does say it does a reload, and I'm sure I did one, but I'm gonna double check.

Rotated at 1805 lines....

C

[akbooer]

@catmanv2 said in Logging lines:

It does say it does a reload

That’s actually coming from AltUI and not the openLuup engine. You definitely have to do an explicit reload.

[CatmanV2]

Pretty sure it's not having it. Forced reload. Log rotate at 1805 lines:

catman@openluup:/etc/cmh-ludl/logs$ cat LuaUPnP.log.1 | wc
   1805   18112  264328

Entry in my Lua Startup

-- Add the log lines
luup.attr_set ("openLuup.Logfile.Lines", 20000)

I assume I've done something stupid....

C

[CatmanV2]

..and again after removing the comment (to be sure) and forcing another reload.

C

[akbooer]

Just remind me which version you’re running.
In fact, better, PM me the startup log.

[akbooer]

...and as a sanity check, look at the Logfile parameters on the console openLuup > System > parameters page, and see that they are what you expect.

[CatmanV2]

The parameters appears to reflect the actuality:

Logfile
Incoming	true
Lines	2000
Name	logs/LuaUPnP.log
Versions	5

C

[CatmanV2]

@akbooer said in Logging lines:

Just remind me which version you’re running.
In fact, better, PM me the startup log.

Can't see how to attach files in pm, and the log is too long for just one chat message. Any reason not to post here?

Cheers

C

[akbooer]

@catmanv2 said in Logging lines:

The parameters appears to reflect the actuality:

Then your Startup Code is wrong, or being changed somewhere else. You don’t have any residual edits left over from trying to fix this earlier?

[akbooer]

@catmanv2 said in Logging lines:

Can't see how to attach files in pm

You can email it to: openLuup at icloud.com

[CatmanV2]

@akbooer said in Logging lines:

@catmanv2 said in Logging lines:

The parameters appears to reflect the actuality:

Then your Startup Code is wrong, or being changed somewhere else. You don’t have any residual edits left over from trying to fix this earlier?

I don't think so. Can't see what else I would have done, or where I would have done it?

-- You can personalise the installation by changing these attributes,
-- which are persistent and may be removed from the Startup after a reload.
local attr = luup.attr_set ("latitude", 51.76)
local attr = luup.attr_set ("City_description", Harlow)
local attr = luup.attr_set ("longitude", 0.13)

-- Geographical location
attr ("City_description", "Harlow")
attr ("Country_description", "UNITED KINGDOM")
attr ("Region_description", "England")
attr ("latitude", "51.76")
attr ("longitude", "0.13")

-- other parameters
attr ("TemperatureFormat", "C")
attr ("PK_AccessPoint", "88800000")
attr ("currency", "£")
attr ("date_format", "dd/mm/yy")
attr ("model", "Not a Vera")
attr ("timeFormat", "24hr")

luup.attr_set ("openLuup.Logfile.Lines", 20000)

-- Any other startup processing may be inserted here...
luup.log "startup code completed"

Do I need to move the line to about the 'startup code completed?

C

[akbooer]

This would rather explain it...

2020-12-08 22:41:12.859   openLuup.context_switch::  ERROR: [dev #0] [string "_openLuup_STARTUP_"]:9: attempt to call local 'attr' (a nil value)
2020-12-08 22:41:12.859   openLuup.init:: ERROR: [string "_openLuup_STARTUP_"]:9: attempt to call local 'attr' (a nil value)

You have a syntax error, and you’re not yet using the startup line I recommended.

[akbooer]

These lines are in error...

local attr = luup.attr_set ("latitude", 51.76)
local attr = luup.attr_set ("City_description", Harlow)
local attr = luup.attr_set ("longitude", 0.13)