Open GoogleCodeExporter opened 8 years ago
GoogleCodeExporter
commented
8 years ago Did you check if your event log is full?
Can you copy here your zig file and the logging file?
I think you should set the debug level only to ERROR and not to DEBUG.
Let us know.Original comment by pco...@gmail.com on 25 Sep 2007 at 7:58
GoogleCodeExporter
commented
8 years ago Thanks...
*Which* event log? The OS one?? Following on from that, how to set from DEBUG to
ERROR? (and out of curiosity how might it have got set to DEBUG in the first
instance?)
Cheers....Original comment by sk...@spamcop.net on 25 Sep 2007 at 2:41
GoogleCodeExporter
commented
8 years ago Check if the OS event log is full first.
If not, it is possible that you reached the maximum file size for a
log (if you are under Windows it should be 2 Gb).
The log is generated in a path according to your zig.file and
logging.config log. Check the zig.file and look where it is located
the logging.config file. Change the DEBUG level to ERROR in the
logging.config file (unluckily it is left to DEBUG in the file
deployed with the installation).
This is the sample zig file that is installed when you install zigGIS:
[connection]
; Your PostgreSQL server.
server = localhost
; Your PostgreSQL server's port.
port = 5432
; Your PostGIS database.
database = TUTORIAL
; Your PostGIS user.
user = psqluser
; Your PostGIS password.
password = psqluser
; Other stuff not used yet.
; ssl = true | false
; pooling = true | false
; minpoolsize =
; maxpoolsize =
; timeout = <wait time for connection in seconds>
; The logging section is optional but recommended.
[logging]
; This is the complete path to the log4net config file.
; An example log4net config file is included. See
; the log4net documentation for more help.
configfile = C:\ziggis\ZigGis\logging.config
According to this zig file the logging config file is under
C:\ziggis\ZigGis\logging.config.
Open the logging.config file that is installed when you install zigGIS
(change LEVEL VALUE to ERROR, or consult log4net docs for more infos):
－
<log4net>
－
<appender name="NormalFile" type="log4net.Appender.FileAppender">
<param name="File" value="C:\\log\\debug.log"/>
<param name="AppendToFile" value="false"/>
－
<layout type="log4net.Layout.PatternLayout">
<param name="ConversionPattern" value="%d [%t] %-5p %c [%x] <%X{auth}> - %m%n"/>
</layout>
</appender>
－
<appender name="RollingFile" type="log4net.Appender.RollingFileAppender">
<param name="File" value="C:\\log\\debug.log"/>
<param name="AppendToFile" value="false"/>
<param name="MaximumFileSize" value="5MB"/>
<param name="MaxSizeRollBackups" value="10"/>
－
<layout type="log4net.Layout.PatternLayout">
<conversionPattern value="%d [%t] %-5p %c [%x] <%X{auth}> - %m%n"/>
</layout>
</appender>
－
<root>
<level value="DEBUG"/>
－
<!--
Either or both of the appenders
described above can be used here.
-->
<appender-ref ref="NormalFile"/>
</root>
－
<!--
There are many ways to configure
log4net. It's urged that the official
log4net documentation is consulted.
-->
</log4net>
If you left the default, you should file your over-sized log file in
C:\\log\\debug.log.
Let me know, and please have patience, remember that zigGIS is OS and
the whole development and support is made on voluntary basis.Original comment by pco...@gmail.com on 25 Sep 2007 at 4:15
GoogleCodeExporter
commented
8 years ago Thank you for your reply...
If I suggested anything else apart from patience, then I apologize... :-) I
recognize that this is OS and am *very* grateful (and impressed!) that you and
the
other volunteers are working on this and continue to do so... and that we all
get to
benefit - and may be help if we can (?) :-)
I reset the CONFIG file to ERROR from DEBUG (the log file was only 5k by the
way..)
After some experimenting, it seems that the error thrown "Error: the event logs
being
full" is *not* in fact the issue...
Instead, it is *certain* spatial datasets I have in my PostgreSQL database that
it
does not like - that is, using exactly the same .zig and .config file for the
connection, (i) some layers add as expected and (ii) some layers (consistently)
don't
add and the "Error: the event logs is full" dialog box appears (and the log
does NOT
have any lines appended to it...)
Just FYI - if I re-add a dataset that seems to work and one that seems to not
(consistently) work in the same 'AddPostGIS data' operation (i.e., checking
multiple
layers), the one that has worked previously gets added as expected AND the
"Error:
the event logs is full" comes up for those that don't want to be added...
Let me know how I can help further, if at all... for instance, I can look at
see what
the difference in the two datasets might be? (different SRID maybe? :-) )
Again, thank you...
Original comment by sk...@spamcop.net on 25 Sep 2007 at 5:03
GoogleCodeExporter
commented
8 years ago OK, FYI, here is the 'issue' it seems...
Some of my project sets stored in a PostGIS format are in State Plane 1983,
Wyoming
West Central, NAD83, US Feet (i.e., not metres) - so there is no EPSG SRID;
using
spatialreference.org, I got the SQL to add a row to my <spatial_ref_sys> for
this
project, ESRI ID is 102757, spatialreference.org IDs uses 9102757 as the SRID
in the
SQL it nicely builds...
MapServer adds this data just fine via a *.map file.
BUT when I try and add the data with this non-EPSG projection to an MXD using
zigGIS
it gives the "Error Log Full" dialogue, no data added... and lets me keep
working...
Does zigGIS have a SRID list I could / should update?
Cheers! GREG... Original comment by sk...@spamcop.net on 5 Oct 2007 at 11:15
GoogleCodeExporter
commented
8 years ago Greg
have you seen this?
http://code.google.com/p/ziggis/issues/detail?id=12
Let me know
Original comment by pco...@gmail.com on 7 Oct 2007 at 9:35
Original issue reported on code.google.com by
sk...@spamcop.neton 24 Sep 2007 at 9:02