Protege fails to update plugins, refers to nonexistent "console log"

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Protege fails to update plugins, refers to nonexistent "console log"

Benjamin Geer
Hello,

I've just installed Protege on Mac OS X, and the first thing it did
after I launched it was try to update some plugins. It then said: "Some
errors found downloading plugins - look at the console log". However, I
don't see anything called "console log" in the user interface.

I thought perhaps this meant that I should try running Protege from a
terminal window. However, both "run.sh" and "run.command" produced other
error messages and failed to launch the application.

Looking at log4j.xml, it seems that errors should actually be logged to
a file in a "logs" directory, but there is no such directory.

I thought the underlying issue might be a permissions issue, so I tried
installing Protege in my home directory instead of under Applications,
but this produced the same result.

Where can I find the mysterious "console log"?

Benjamin Geer
Digital Humanities Lab
University of Basel

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Protege fails to update plugins, refers to nonexistent "console log"

Timothy Redmond

The "console log" mentioned is an OS X application (I think it is in
Applications/Utilities) and it is often one of the places where the logs
can be read.  But a more reliable place is in the directory
~/.Protege/logs where ~ represents your home directory. The logs rotate
and old ones are deleted.

-Timothy

On 03/26/2014 05:59 AM, Benjamin Geer wrote:

> Hello,
>
> I've just installed Protege on Mac OS X, and the first thing it did
> after I launched it was try to update some plugins. It then said:
> "Some errors found downloading plugins - look at the console log".
> However, I don't see anything called "console log" in the user interface.
>
> I thought perhaps this meant that I should try running Protege from a
> terminal window. However, both "run.sh" and "run.command" produced
> other error messages and failed to launch the application.
>
> Looking at log4j.xml, it seems that errors should actually be logged
> to a file in a "logs" directory, but there is no such directory.
>
> I thought the underlying issue might be a permissions issue, so I
> tried installing Protege in my home directory instead of under
> Applications, but this produced the same result.
>
> Where can I find the mysterious "console log"?
>
> Benjamin Geer
> Digital Humanities Lab
> University of Basel
>
> _______________________________________________
> protege-user mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-user

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user
Reply | Threaded
Open this post in threaded view
|

Re: Protege fails to update plugins, refers to nonexistent "console log"

Benjamin Geer
Thanks for this clarification. I've attached the log file from the
~/.Protege/logs directory. It doesn't seem to provide any information on
the problem, beyond saying "Could not download plugin".

Ben

On 26/03/14 16:21, Timothy Redmond wrote:

>
> The "console log" mentioned is an OS X application (I think it is in
> Applications/Utilities) and it is often one of the places where the
> logs can be read.  But a more reliable place is in the directory
> ~/.Protege/logs where ~ represents your home directory. The logs
> rotate and old ones are deleted.
>
> -Timothy
>
> On 03/26/2014 05:59 AM, Benjamin Geer wrote:
>> Hello,
>>
>> I've just installed Protege on Mac OS X, and the first thing it did
>> after I launched it was try to update some plugins. It then said:
>> "Some errors found downloading plugins - look at the console log".
>> However, I don't see anything called "console log" in the user
>> interface.
>>
>> I thought perhaps this meant that I should try running Protege from a
>> terminal window. However, both "run.sh" and "run.command" produced
>> other error messages and failed to launch the application.
>>
>> Looking at log4j.xml, it seems that errors should actually be logged
>> to a file in a "logs" directory, but there is no such directory.
>>
>> I thought the underlying issue might be a permissions issue, so I
>> tried installing Protege in my home directory instead of under
>> Applications, but this produced the same result.
>>
>> Where can I find the mysterious "console log"?
>>
>> Benjamin Geer
>> Digital Humanities Lab
>> University of Basel
>>
>> _______________________________________________
>> protege-user mailing list
>> [hidden email]
>> https://mailman.stanford.edu/mailman/listinfo/protege-user
>
> _______________________________________________
> protege-user mailing list
> [hidden email]
> https://mailman.stanford.edu/mailman/listinfo/protege-user

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user

protege-0.log (4K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: Protege fails to update plugins, refers to nonexistent "console log"

Timothy Redmond
On 03/31/2014 12:54 AM, Benjamin Geer wrote:
Thanks for this clarification. I've attached the log file from the ~/.Protege/logs directory. It doesn't seem to provide any information on the problem, beyond saying "Could not download plugin".

I haven't quite figured out what is going on with that log.  It is not clear how you can be downloading the dl query plugin when you already have it installed.  As long as the bug doesn't keep repeating, it should be ok because I don't believe that there is an update to that plugin that you need.

-Timothy.



Ben

On 26/03/14 16:21, Timothy Redmond wrote:

The "console log" mentioned is an OS X application (I think it is in Applications/Utilities) and it is often one of the places where the logs can be read.  But a more reliable place is in the directory ~/.Protege/logs where ~ represents your home directory. The logs rotate and old ones are deleted.

-Timothy

On 03/26/2014 05:59 AM, Benjamin Geer wrote:
Hello,

I've just installed Protege on Mac OS X, and the first thing it did after I launched it was try to update some plugins. It then said: "Some errors found downloading plugins - look at the console log". However, I don't see anything called "console log" in the user interface.

I thought perhaps this meant that I should try running Protege from a terminal window. However, both "run.sh" and "run.command" produced other error messages and failed to launch the application.

Looking at log4j.xml, it seems that errors should actually be logged to a file in a "logs" directory, but there is no such directory.

I thought the underlying issue might be a permissions issue, so I tried installing Protege in my home directory instead of under Applications, but this produced the same result.

Where can I find the mysterious "console log"?

Benjamin Geer
Digital Humanities Lab
University of Basel

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user

_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user



_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user


_______________________________________________
protege-user mailing list
[hidden email]
https://mailman.stanford.edu/mailman/listinfo/protege-user