Nick - I know this stuff can be frustrating. Less cryptic answer follows......
1. When you edit a file and then immediately a problem occurs I'd suggest you might perhaps take a breath and (re)read the error messages like these when you see them...because they really 'do' tell you where you need to look to find the cause of the problem you're running into. > Using configuration file /etc/weewx/weewx.conf > [...] > configobj.DuplicateError: Duplicate section name at line 350 So a reasonable thing is to look around line 350 in weewx.conf for a [section] that exists above in that file. ==> That's the file you touched. ==> That's almost certainly the file you typo'd within. 2. If the error messages don't make sense, take a minute to use google search. Just search for your error message. - A Google search for "configobj.DuplicateError: Duplicate section name at line 350" returned the following: configobj.DuplicateError: Duplicate section name at line 350 indicates that the configuration file you are trying to read has two or more sections with the exact same name, and the configobj library is running in a mode where this is not allowed. [...] Edit the configuration file: Open the configuration file (usually an INI file) in a text editor. Go to line 350 and the original line with the same section name. You will need to either rename one of the sections to be unique or remove the duplicate if it is unnecessary. ==> so it's saying you have a duplicate [something] around line 350, which is almost certainly in the area you were hand-editing. 3. Alternately leverage the nice search capability of the google group here.... - A search in this google group for "configobj.DuplicateError: Duplicate section name at line" (omitting the line number) returns a number of hits dating back over a decade including at least a couple that were identical and had answers saying basically '*you have [whatever] twice in your file*'. Bottom line is that most of this stuff isn't 'that' difficult usually if you just use the search capabilities and a little common sense (or coffee, or walking away for a bit rather than getting frustrated). ==> If you edit file XYZ and break something, it is pretty likely that file XYZ is where the typo/error is located. ==> Do things one step at a time in an orderly manner. Save the previous version so you can go back to the last working copy, Learn to use the 'diff' utility to compare two versions of a particular file. It really does help. -- You received this message because you are subscribed to the Google Groups "weewx-user" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/d/msgid/weewx-user/9dd2ba5e-d44e-40f9-a032-28994b3a1e0bn%40googlegroups.com.
