Problems with lex

[Former user]

Hi when i try to run monit after installed it with:

apt-get install libssl-dev
apt-get install automake
apt-get install libtool

wget http://mmonit.com/monit/dist/monit-5.11.tar.gz
tar -zxvf monit-5.11.tar.gz
./configure --without-pam
make
make install

i had this issue: "input in flex scanner failed"

on

Linux ... 3.13.0-40-generic #69-Ubuntu SMP Thu Nov 13 17:53:56 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

The configuration file is in ~/.monitrc and is the same file inside monit folder

monit -v gives me the same error

I tried to reinstall it but with no success

[Tildeslash]

Hello,

i'm unable to reproduce the problem, please can you send config.log + make output + your monit configuration file to [e-mail]?

Note that you can also install the PAM headers and compile with PAM:

sudo apt-get install libpam0g-dev
cd monit-5.11
make clean
./configure
make
make install

You can get the pre-compiled binaries here: http://mmonit.com/monit/#download

[Tildeslash]

unable to reproduce, no data from the user who reported, most probably environment issue -> closing

[Former user]

Hi, I'm playing around with monit 5.14 for Linux ARM and am having similar issues.

I'm able to install monit using aptitude (also had to downgrade my libpam0g-dev, which I learned to do from this above in this thread) and I can view monit from the httpd server but any terminal interactions with my daemonized monit return the error "input in flex scanner failed" (and the actions do not complete). This appears to be only thing not currently working with my monit install.

Thanks!

[Tildeslash]

Could you provide us with a minimum monitors file which reproduces the error and the flex version used to build Monit?

If you have time, could you also try the prebuilt binary for Linux ARM download and see if the problem is there as well?

[Former user]

Thanks for the quick reply! Could you please clarify what you mean by "minimum monitors file" ? I am guessing you're speaking about the monit config file containing the "rules".

Executing flex --version yields /flex 2.5.35

In the mean time I will download the ARM binary and see if I get similar results.

Edit: Ok I tried the ARM binary and I couldn't event get it to execute on my TI OMAP development machine: no errors or anything. I used tar -xzvf to extract and I ensured the file had execute permissions as well. This was after I removed my existing monit install from /etc/inittab.

I then uninstalled all instances of monit and retrieved the source, and then installed using ./configure; make; make install (had to also install libssl-dev this time). It's now working again (as it was before), but I still cant interact with it via the terminal. Getting the same input in flex scanner failed message.

I have also reduced my monitrc file to the following:

###############################################################################
## Global section
###############################################################################
##
## Start Monit in the background (run as a daemon):

set daemon  30              # check services at 30 seconds intervals

## Monit has an embedded HTTP interface which can be used to view status of 
## services monitored and manage services from a web interface. The HTTP 
## interface is also required if you want to issue Monit commands from the
## command line, such as 'monit status' or 'monit restart service' The reason
## for this is that the Monit client uses the HTTP interface to send these
## commands to a running Monit daemon. See the Monit Wiki if you want to 
## enable SSL for the HTTP interface. 
#
set httpd port 2812 and
    allow admin:monit      # require user 'admin' with password 'monit'

[Tildeslash]

Exactly that, a monitrcfile with one or more rules we can use to try and reproduce the problem.

[Tildeslash]

You mention that you use TI OMAP. We have only tested Monit ARM builds on Raspberry and have no experience with TI OMAP, unfortunately. Since we cannot reproduce on our HW it is hard to debug this problem. A quick search for the phrase "input in flex scanner failed" does seem to indicate that this could be caused be a subtle problem in the lexer interface. But until we can find a reliably way to reproduce the error it is difficult for us to attempt to debug and fix it.

[Former user]

Ok, thanks anyways. I think my team has decided to move away from monit in favor of PCD for our TI OMAP application. However I am using monit on several of our development machines and loving the results.

Keep up the great work!