[CWB] CQPweb: $path_to_cwb (config) vs. $path_to_cqp (system diagnostics)

Markus Killer markus.killer at uzh.ch
Tue Jan 21 13:39:04 CET 2014 

that was 510. will perform check with 511 in a minute ...

----------------------------------------
> From: a.hardie at lancaster.ac.uk
> To: cwb at sslmit.unibo.it
> Date: Tue, 21 Jan 2014 12:36:32 +0000
> Subject: Re: [CWB] CQPweb: $path_to_cwb (config) vs. $path_to_cqp (system diagnostics)
>
> Was that with revision 511 or 510? The fix for that went in 511, or at least I *thought* it had.
>
> Andrew.
>
> -----Original Message-----
> From: cwb-bounces at sslmit.unibo.it [mailto:cwb-bounces at sslmit.unibo.it] On Behalf Of Markus Killer
> Sent: 21 January 2014 12:32
> To: cwb at sslmit.unibo.it
> Subject: [CWB] CQPweb: $path_to_cwb (config) vs. $path_to_cqp (system diagnostics)
>
> Thanks for your quick fixes. Fully understand that you have other things to do.
>
> Found my mistake (used wrong variable in config: $path_to_cqp), changed it to $path_to_cwb and have now working backend with newly generated skins and colours.
>
> But for me to be able to login as superuser after autosetup terminates with:
>
> Database setup complete.
> PHP Warning: mysql_close(): 13 is not a valid MySQL-Link resource in /var/www/cqp-web-beta/lib/library.inc.php on line 152 Invalid user name specified at database level: mkiller
>
>
> I still have to manually add something like this to the database (table: user_info):
>
> INSERT INTO cqpwbeta.user_info (username, passhash, acct_status) VALUES ('mkiller','$2a$10/1ZOmv****CZWu2qedq','1');
>
>
>
>
>
>
>
> ________________________________
>> From: markus.killer at uzh.ch
>> To: a.hardie at lancaster.ac.uk
>> Subject: RE: [CWB] CWB Digest, Vol 84, Issue 7
>> Date: Tue, 21 Jan 2014 11:25:52 +0100
>>
>>
>> sorry, that's my bad (forgot about p17)
>>
>> But the error still persists after manually adding the path to the
>> config file (attached), I can't regenerate the skins and when I run 'system diagnostics' - 'Check CQP backend'
>> the path is still an empty string (I double checked that the updated config.inc.php was used):
>>
>> Beginning diagnostics on CQP child process connection.
>>
>> Using following configuration variables:
>> $path_to_cqp = ``''
>> $cwb_registry = ``/home/mki/cqp_web_beta_data/registry''
>>
>> Checking that exists...
>> CHECK FAILED. Check that exists and contains the CQP executable.
>>
>>
>> ________________________________
>>> From: a.hardie at lancaster.ac.uk
>>> To: cwb at sslmit.unibo.it
>>> Date: Tue, 21 Jan 2014 09:58:26 +0000
>>> Subject: Re: [CWB] CWB Digest, Vol 84, Issue 7
>>>
>>>
>>> $path_to_cwb is no longer compulsory and the config script only sets
>>> up compulsory variables. That's why it's no longer asked for.
>>>
>>>
>>>
>>> If you don't add it manually to your config file, then it is assumed
>>> that CQP is on the path. If it's not, then conversely you need to add
>>> it to your config file.
>>>
>>>
>>>
>>> See manual page 24, also pg 17.
>>>
>>>
>>>
>>> best
>>>
>>>
>>>
>>> Andrew.
>>>
>>>
>>>
>>> From: Markus Killer [mailto:markus.killer at uzh.ch]
>>> Sent: 21 January 2014 09:55
>>> To: Hardie, Andrew
>>> Subject: RE: [CWB] CWB Digest, Vol 84, Issue 7
>>>
>>>
>>>
>>> The problem exists on new installs as well: attached you'll find the config-file generated by autoconfig-script ($path_to_cqp is missing and autoconfig doesn't ask for it).
>>>
>>> This is how I was able to log into the admin panel, eventually (did the same as Unmut):
>>>
>>> manually added superuser to db, then logged into admin panel & tried to generate skins:
>>>
>>> ERROR: CQP backend startup failed
>>> Then, ran 'system diagnostics' - 'Check CQP backend':
>>>
>>> Beginning diagnostics on CQP child process connection.
>>>
>>> Using following configuration variables:
>>> $path_to_cqp = ``''
>>> $cwb_registry = ``/home/mki/cqp_web_beta_data/registry''
>>>
>>> Checking that exists...
>>> CHECK FAILED. Check that exists and contains the CQP executable.
>>>
>>> ----------------------------------------
>>>> From: a.hardie at lancaster.ac.uk<mailto:a.hardie at lancaster.ac.uk>
>>>> To: cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>
>>>> Date: Tue, 21 Jan 2014 09:46:57 +0000
>>>> Subject: Re: [CWB] CWB Digest, Vol 84, Issue 7
>>>>
>>>> For the benefit of others - Umut's problem was due to not updating
>>>> the config file to match the new format. The changes ot the config
>>>> file format are described in the manual
>>>>
>>>> http://cwb.sourceforge.net/files/CQPwebAdminManual.pdf
>>>>
>>>> see pages 24 and 25 especually.
>>>>
>>>> best
>>>>
>>>> Andrew.
>>>>
>>>> -----Original Message-----
>>>> From:
>>>> cwb-bounces at sslmit.unibo.it<mailto:cwb-bounces at sslmit.unibo.it>
>>>> [mailto:cwb-bounces at sslmit.unibo.it] On Behalf Of Hardie, Andrew
>>>> Sent: 21 January 2014 07:53
>>>> To: Open source development of the Corpus WorkBench
>>>> Subject: Re: [CWB] CWB Digest, Vol 84, Issue 7
>>>>
>>>> Umut,
>>>>
>>>> Can you please copy the contents of your config file into an email
>>>> to me off-list? (redacting any passwords of course)
>>>>
>>>> I suspect the problem is in there.
>>>>
>>>> best
>>>>
>>>> Andrew.
>>>>
>>>> -----Original Message-----
>>>> From:
>>>> cwb-bounces at sslmit.unibo.it<mailto:cwb-bounces at sslmit.unibo.it>
>>>> [mailto:cwb-bounces at sslmit.unibo.it] On Behalf Of Umut Demirhan
>>>> Sent: 21 January 2014 07:49
>>>> To: cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>
>>>> Subject: Re: [CWB] CWB Digest, Vol 84, Issue 7
>>>>
>>>> Dear Andrew,
>>>>
>>>> Thanks for the recent update. I've upgraded my local CQPweb to 3.1.
>>>>
>>>> After updating, I had several problems. I'm not sure if others have the same issues.
>>>>
>>>> First of all, it is about the user system that Markus reported, and
>>>> you mentoned on twitter. The auto setup script generates the same
>>>> error on my
>>>> x64 Ubuntu, mysql-server-5.5.
>>>>
>>>> I created a normal user and then logged into mysql via phpmyadmin. I changed the name of the user to what I previously selected as superuser, and specified a password for him, and validated the account.
>>>>
>>>> Then, I tried to login to CQPweb, and this time it was successful. I tried to regenerate the color schemas; however, the application generated another error message "CQP backend failed". I checked out the config file and it seems that there is no statement about the paths below:
>>>>
>>>> /* variables do require a '/' before and after */ $path_to_cwb =
>>>> 'usr/local/bin'; $path_to_perl = 'usr/bin';
>>>>
>>>> I've added them to my config file; however, there is no success. It still generates the error message as in below:
>>>> Checking that usr/local/bin/ exists...
>>>> CHECK FAILED. Check that usr/local/bin/ exists and contains the CQP executable.
>>>>
>>>> I'm sure about that the file is located in that folder.
>>>>
>>>> I hope that helps to solve the problem. Does anyone have the same issues?
>>>>
>>>> Best regards,
>>>> Umut
>>>>
>>>>> -----Original Message-----
>>>>> From:
>>>>> cwb-bounces at sslmit.unibo.it<mailto:cwb-bounces at sslmit.unibo.it>
>>>>> [mailto:cwb-bounces at sslmit.unibo.it]
>>>>> On Behalf Of
>>>>> cwb-request at sslmit.unibo.it<mailto:cwb-request at sslmit.unibo.it>
>>>>> Sent: Tuesday, January 21, 2014 6:12 AM
>>>>> To: cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>
>>>>> Subject: CWB Digest, Vol 84, Issue 7
>>>>>
>>>>> Send CWB mailing list submissions to
>>>>> cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>
>>>>>
>>>>> To subscribe or unsubscribe via the World Wide Web, visit
>>>>> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
>>>>> or, via email, send a message with subject or body 'help' to
>>>>> cwb-request at sslmit.unibo.it<mailto:cwb-request at sslmit.unibo.it>
>>>>>
>>>>> You can reach the person managing the list at
>>>>> cwb-owner at sslmit.unibo.it<mailto:cwb-owner at sslmit.unibo.it>
>>>>>
>>>>> When replying, please edit your Subject line so it is more specific
>>>>> than
>>>> "Re:
>>>>> Contents of CWB digest..."
>>>>>
>>>>>
>>>>> Today's Topics:
>>>>>
>>>>> 1. Re: CQPweb: v 3.1.0 now usable, I think (Markus Killer) 2. Re:
>>>>> CQPweb: v 3.1.0 now usable, I think (Hardie, Andrew)
>>>>>
>>>>>
>>>>> -------------------------------------------------------------------
>>>>> ---
>>>>>
>>>>> Message: 1
>>>>> Date: Mon, 20 Jan 2014 20:24:44 +0100
>>>>> From: Markus Killer
>>>>> <markus.killer at uzh.ch<mailto:markus.killer at uzh.ch>>
>>>>> To: "cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>"
>>>>> <cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>>
>>>>> Subject: Re: [CWB] CQPweb: v 3.1.0 now usable, I think
>>>>> Message-ID:
>>>>> <DUB111-W1250365E6838858B54A58968AA50 at phx.gbl<mailto:DUB111-W125036
>>>>> 5E6838858B54A58968AA50 at phx.gbl>>
>>>>> Content-Type: text/plain; charset="iso-8859-1"
>>>>>
>>>>> Dear Andrew,
>>>>> Thanks a lot for the update to v3.1.0. Today, I've successfully
>>>>> installed
>>>> and
>>>>> configured v3.0.16 on a Xubuntu 12.04 LTS (64-bit) system. However,
>>>>> I
>>>> didn't
>>>>> manage to get v3.1.0 (svn rev 497) running. When I try to run the
>>>> autosetup
>>>>> script, I get the following php notices and a fatal error:$php
>>>> autosetup.php
>>>>> PHP Notice: Undefined offset: 1 in /var/www/cqp-web-
>>>>> beta/lib/defaults.inc.php on line 446 PHP Notice: Undefined offset:
>>>>> 1 in /var/www/cqp-web-beta/lib/defaults.inc.php on line 446 PHP Fatal error:
>>>>> Call to a member function is_admin() on a non-object in
>>>>> /var/www/cqp- web-beta/lib/exiterror.inc.php on line 282 I then
>>>>> went on to try an
>>>> upgrade
>>>>> from v3.0.16, but the update upgrade-database.php script terminates
>>>>> with the same php fatal error.Best wishes,Markus [CWB] CQPweb: v
>>>>> 3.1.0 now usable, I thinkHardie, Andrew a.hardie at lancaster.ac.uk
>>>>> Mon Jan
>>>>> 20 09:19:41 CET 2014Previous message: [CWB] [cwb:bugs] #60 CQPweb :
>>>>> metadata from XML, primary classification not setNext message:
>>>>> [CWB] CQPweb: v 3.1.0 now usable, I thinkMessages sorted by: [ date
>>>>> ] [ thread ] [ subject ] [ author ]Hi all,
>>>>>
>>>>> My grand re-structuring of almost everything for CQPweb v 3.1.0 is
>>>>> now finished.
>>>>>
>>>>> There is not much visible difference, but a lot has changed under
>>>>> the
>>>> bonnet,
>>>>> and this will hopefully make it quicker and easier to implement new
>>>> features.
>>>>>
>>>>> If you are an adventurous sort, I think you can now safely upgrade
>>>>> to
>>>> 3.1.0
>>>>> (repo commit 497). There are probably bugs; reports very welcome.
>>>>>
>>>>> If you are less adventurous, you might want to stick with 3.0.16 a
>>>>> bit
>>>> longer,
>>>>> until the worst problems are dealt with.
>>>>>
>>>>> Currently 3.1 runs nowhere but on my computer. Later today I hope
>>>>> to upgrade the Lancaster to 3.1, so those of you with accounts on
>>>>> that server can have a look at it later this week to see what has changed.
>>>>>
>>>>> One big change that you won't see from looking at a server is that
>>>>> I have completely revamped the sysadmin documentation. Previously
>>>>> this consisted of a series of HTML files - the maintenance of which
>>>>> has become increasingly hairy over the past couple of years. Now, I
>>>>> have shifted most
>>>> of
>>>>> these over into a "CQPweb System Administrator's Manual" written in
>>>>> LaTeX and available within the usual documentation tree on the
>>>>> SourceForge repository. I hope that this new format will (a) make
>>>>> it more maintainable
>>>> (b)
>>>>> make it easier for others to contribute patches. There are still a
>>>>> couple
>>>> of
>>>>> HTML files to convert; these will be done as and when I find a moment.
>>>>>
>>>>> Like the CWB and CQP tutorials, the manual compiles to both PDF and
>>>>> HTML; the PDF is included with CQPweb and is also on the website here:
>>>>>
>>>>> http://cwb.sourceforge.net/files/CQPwebAdminManual.pdf
>>>>>
>>>>> Crucially, it has a couple of sections that between them cover the
>>>>> process
>>>> of
>>>>> upgrading from v 3.0.16 to 3.1.0, which, given all the changes I
>>>>> have
>>>> made, is
>>>>> non-straightforward.
>>>>>
>>>>> That's all for now.
>>>>>
>>>>> best
>>>>>
>>>>> Andrew.
>>>>> -------------- next part -------------- An HTML attachment was
>>>>> scrubbed...
>>>>> URL:
>>>>> <http://devel.sslmit.unibo.it/pipermail/cwb/attachments/20140120/aa
>>>>> 040
>>>>> e3
>>>>> b/attachment-0001.html>
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> Message: 2
>>>>> Date: Tue, 21 Jan 2014 04:12:06 +0000
>>>>> From: "Hardie, Andrew"
>>>>> <a.hardie at lancaster.ac.uk<mailto:a.hardie at lancaster.ac.uk>>
>>>>> To: "m.killer at outlook.com<mailto:m.killer at outlook.com>"
>>>>> <m.killer at outlook.com<mailto:m.killer at outlook.com>>, "Open source
>>>>> development of the Corpus WorkBench"
>>>>> <cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>>
>>>>> Subject: Re: [CWB] CQPweb: v 3.1.0 now usable, I think
>>>>> Message-ID:
>>>>> <28078EC3FBF1B940A3EF3D0D19BE351D2CCD39 at EX-0-
>>>>> MB1.lancs.local>
>>>>> Content-Type: text/plain; charset="us-ascii"
>>>>>
>>>>> Thanks for the bug report; sorry for delay responding. This turned
>>>>> out to
>>>> be a
>>>>> lingering environment bug from a much earlier version that was
>>>>> newly exposed by the new scripts. Now fixed in svn.
>>>>>
>>>>> best
>>>>>
>>>>> Andrew.
>>>>>
>>>>> From:
>>>>> cwb-bounces at sslmit.unibo.it<mailto:cwb-bounces at sslmit.unibo.it>
>>>>> [mailto:cwb-bounces at sslmit.unibo.it]
>>>>> On Behalf Of Markus Killer
>>>>> Sent: 20 January 2014 19:25
>>>>> To: cwb at sslmit.unibo.it<mailto:cwb at sslmit.unibo.it>
>>>>> Subject: Re: [CWB] CQPweb: v 3.1.0 now usable, I think
>>>>>
>>>>>
>>>>> Dear Andrew,
>>>>>
>>>>>
>>>>>
>>>>> Thanks a lot for the update to v3.1.0. Today, I've successfully
>>>>> installed
>>>> and
>>>>> configured v3.0.16 on a Xubuntu 12.04 LTS (64-bit) system. However,
>>>>> I
>>>> didn't
>>>>> manage to get v3.1.0 (svn rev 497) running.
>>>>>
>>>>> When I try to run the autosetup script, I get the following php
>>>>> notices
>>>> and a
>>>>> fatal error:
>>>>>
>>>>> $php autosetup.php
>>>>>
>>>>> PHP Notice: Undefined offset: 1 in /var/www/cqp-web-
>>>>> beta/lib/defaults.inc.php on line 446
>>>>>
>>>>> PHP Notice: Undefined offset: 1 in /var/www/cqp-web-
>>>>> beta/lib/defaults.inc.php on line 446
>>>>>
>>>>> PHP Fatal error: Call to a member function is_admin() on a
>>>>> non-object in /var/www/cqp-web-beta/lib/exiterror.inc.php on line
>>>>> 282
>>>>>
>>>>> I then went on to try an upgrade from v3.0.16, but the update
>>>>> upgrade- database.php script terminates with the same php fatal error.
>>>>>
>>>>> Best wishes,
>>>>>
>>>>> Markus
>>>>>
>>>>>
>>>>>
>>>>> [CWB] CQPweb: v 3.1.0 now usable, I think Hardie, Andrew a.hardie
>>>>> at lancaster.ac.uk
>>>>> <mailto:cwb%40sslmit.unibo.it?Subject=Re:%20Re%3A%20%5BCWB%5D%20
>>> <mailto:cwb%40sslmit.unibo.it?Subject=Re:%20Re%3A%20%5BCWB%5D%20%0b>>
>>>> CQPweb%3A%20v%203.1.0%20now%20usable%2C%20I%20think&In-Reply-
>>>>> To=%3C28078EC3FBF1B940A3EF3D0D19BE351D2CC631%40EX-0-
>>>>> MB1.lancs.local%3E>
>>>>> Mon Jan 20 09:19:41 CET 2014
>>>>>
>>>>> * Previous message: [CWB] [cwb:bugs] #60 CQPweb : metadata from
>>>>> XML, primary classification not
>>>>> set<http://devel.sslmit.unibo.it/pipermail/cwb/2014-January/001480.
>>>>> html>
>>>>> * Next message: [CWB] CQPweb: v 3.1.0 now usable, I
>>>>> think<http://devel.sslmit.unibo.it/pipermail/cwb/2014-
>>>>> January/001482.html>
>>>>> * Messages sorted by: [ date
>>>>> ]<http://devel.sslmit.unibo.it/pipermail/cwb/2014-January/date.html
>>>>> #14
>>>>> 81> [ thread ]<http://devel.sslmit.unibo.it/pipermail/cwb/2014-
>>>>> January/thread.html#1481> [ subject
>>>>> ]<http://devel.sslmit.unibo.it/pipermail/cwb/2014-
>>>>> January/subject.html#1481> [ author
>>>>> ]<http://devel.sslmit.unibo.it/pipermail/cwb/2014-
>>>>> January/author.html#1481>
>>>>>
>>>>> ________________________________
>>>>>
>>>>> Hi all,
>>>>>
>>>>>
>>>>>
>>>>> My grand re-structuring of almost everything for CQPweb v 3.1.0 is
>>>>> now finished.
>>>>>
>>>>>
>>>>>
>>>>> There is not much visible difference, but a lot has changed under
>>>>> the
>>>> bonnet,
>>>>> and this will hopefully make it quicker and easier to implement new
>>>> features.
>>>>>
>>>>>
>>>>>
>>>>> If you are an adventurous sort, I think you can now safely upgrade
>>>>> to
>>>> 3.1.0
>>>>> (repo commit 497). There are probably bugs; reports very welcome.
>>>>>
>>>>>
>>>>>
>>>>> If you are less adventurous, you might want to stick with 3.0.16 a
>>>>> bit
>>>> longer,
>>>>> until the worst problems are dealt with.
>>>>>
>>>>>
>>>>>
>>>>> Currently 3.1 runs nowhere but on my computer. Later today I hope
>>>>> to upgrade the Lancaster to 3.1, so those of you with accounts on
>>>>> that server can have a look at it later this week to see what has changed.
>>>>>
>>>>>
>>>>>
>>>>> One big change that you won't see from looking at a server is that
>>>>> I have completely revamped the sysadmin documentation. Previously
>>>>> this consisted of a series of HTML files - the maintenance of which
>>>>> has become increasingly hairy over the past couple of years. Now, I
>>>>> have shifted most
>>>> of
>>>>> these over into a "CQPweb System Administrator's Manual" written in
>>>>> LaTeX and available within the usual documentation tree on the
>>>>> SourceForge repository. I hope that this new format will (a) make
>>>>> it more maintainable
>>>> (b)
>>>>> make it easier for others to contribute patches. There are still a
>>>>> couple
>>>> of
>>>>> HTML files to convert; these will be done as and when I find a moment.
>>>>>
>>>>>
>>>>>
>>>>> Like the CWB and CQP tutorials, the manual compiles to both PDF and
>>>>> HTML; the PDF is included with CQPweb and is also on the website here:
>>>>>
>>>>>
>>>>>
>>>>> http://cwb.sourceforge.net/files/CQPwebAdminManual.pdf
>>>>>
>>>>>
>>>>>
>>>>> Crucially, it has a couple of sections that between them cover the
>>>>> process
>>>> of
>>>>> upgrading from v 3.0.16 to 3.1.0, which, given all the changes I
>>>>> have
>>>> made, is
>>>>> non-straightforward.
>>>>>
>>>>>
>>>>>
>>>>> That's all for now.
>>>>>
>>>>>
>>>>>
>>>>> best
>>>>>
>>>>>
>>>>>
>>>>> Andrew.
>>>>> -------------- next part -------------- An HTML attachment was
>>>>> scrubbed...
>>>>> URL:
>>>>> <http://devel.sslmit.unibo.it/pipermail/cwb/attachments/20140121/df
>>>>> 61a
>>>>> 72
>>>>> e/attachment.html>
>>>>>
>>>>> ------------------------------
>>>>>
>>>>> _______________________________________________
>>>>> CWB mailing list
>>>>> CWB at sslmit.unibo.it<mailto:CWB at sslmit.unibo.it>
>>>>> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
>>>>>
>>>>>
>>>>> End of CWB Digest, Vol 84, Issue 7
>>>>> **********************************
>>>>
>>>> _______________________________________________
>>>> CWB mailing list
>>>> CWB at sslmit.unibo.it<mailto:CWB at sslmit.unibo.it>
>>>> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
>>>> _______________________________________________
>>>> CWB mailing list
>>>> CWB at sslmit.unibo.it<mailto:CWB at sslmit.unibo.it>
>>>> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
>>>> _______________________________________________
>>>> CWB mailing list
>>>> CWB at sslmit.unibo.it<mailto:CWB at sslmit.unibo.it>
>>>> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
>>>
>>> _______________________________________________ CWB mailing list
>>> CWB at sslmit.unibo.it http://devel.sslmit.unibo.it/mailman/listinfo/cwb
> _______________________________________________
> CWB mailing list
> CWB at sslmit.unibo.it
> http://devel.sslmit.unibo.it/mailman/listinfo/cwb
> _______________________________________________
> CWB mailing list
> CWB at sslmit.unibo.it
> http://devel.sslmit.unibo.it/mailman/listinfo/cwb

More information about the CWB mailing list