InfiniDB4.5 without Apache Installation Issue

8 posts / 0 new
Last post
james_Shen
james_Shen's picture
Offline
Last seen: 3 months 1 day ago
Joined: Apr 8 2014
Junior Boarder

Posts: 2

James Shen
InfiniDB4.5 without Apache Installation Issue

I meet a strange issue when installing InfiniDB4.5 on CentOS6.5.

 

Installation Env:

     OS: CentOS6.5

     3 Nodes(1 UM,2 PM,Seperate,Mutiple server mode)

     No firewall

 

Installation Scenario is OK except error information(dummy package is not install)  --I used to install without dummy package before,seems OK with this dummy package.

 

But at last step, InfiniDB can not started.Following is installation log and error log,can anyone help.

 

Thanks!

 

 

Log information:

Installation log:

----- Starting InfiniDB on 'um1' -----
 
InfiniDB successfully started
 
----- Starting InfiniDB on 'pm2' -----
 
InfiniDB successfully started
 
----- Starting InfiniDB on local server -----
 
InfiniDB successfully started
 
InfiniDB Database Platform Starting, please wait ......................................................................................................................... FAILED
 
InfiniDB System failed to start, check log files in /var/log/Calpont

 

 

 

error.log:

Apr 23 17:22:12 ntgtstapp14 ProcessMonitor[2530]: 12.785683 |0|0|0| E 18 CAL0000: checkDataMount: mount failed, dbroot: /usr/local/Calpont/data1         
Apr 23 17:22:12 ntgtstapp14 oamcpp[2606]: 12.817058 |0|0|0| E 08 CAL0000: getSystemStatus: write exception: InetStreamSocket::connect: connect() error: Connection refus
ed to: InetStreamSocket: sd: 4 inet: 10.215.70.160 port: 8604         
Apr 23 17:22:12 ntgtstapp14 oamcpp[2606]: 12.822798 |0|0|0| E 08 CAL0000: getSystemStatus: MessageQueueClient exception: API Failure return in getSystemStatus API      
 
 
 
 
davidhill
davidhill's picture
Offline
Last seen: 1 day 1 hour ago
Joined: Oct 27 2009
Administrator

Posts: 595

david hill
Hey James, here is some

Hey James, here is some things to check.

 

1. For starters, ignore the 'dmmy' package reference in the install logs, that is just a dumy command.

2. From the logs, I beleive the error that is causing the failure is the failure to mount error, which means you specified exteranl storage type in postConfigure.

    External storage types requires the user to setup mounts in /etc/fstab or manually on the command line to mount to the data directories. Check the installtion

    documenetaion for further information.

    If you don't have external storage and you want to store on the lcoal servers, then you will need to re-run postConfigure and specifcy 'internal' storage.

 

David Hill  (InfiniDB)

james_Shen
james_Shen's picture
Offline
Last seen: 3 months 1 day ago
Joined: Apr 8 2014
Junior Boarder

Posts: 2

James Shen
Hi David, 

Hi David,
 

     I have solved this issue as what you told me.Really appreciate.

   

     But I another issue when I do POC for InifiniDB like that:

        We load 30M data into InfiniDB (1 UM,2PM, separate mode),and we use “select count(distinct)” to calculate on 30M data, issue pops up like “ERROR 122 (HY000): IDB-2003: Aggregation/Distinct memory limit is exceeded.”.

 

      I think data volume is not so huge for "Big data",but InfiniDB gives me this error.I don't know if there is any configuration parameter for handling this issue.

 

 

    Thanks!

radams
radams's picture
Offline
Last seen: 1 hour 40 min ago
Joined: Jan 3 2011
Administrator

Posts: 487

Robert Adams
Aggregation/Distinct memory limit is exceeded

 

Hi James,

 

The setting TotalUmMemory is the setting that is controls this.

 

Please consult the Tuning Guide for information on this changing this setting.

 

Thanks,

 

Robert

 

 

marinakr
marinakr's picture
Offline
Last seen: 2 months 2 weeks ago
Joined: Dec 27 2013
Junior Boarder

Posts: 6

Marina Victoria
Error postConfigure

[quote=davidhill]

Hey James, here is some things to check. 1. For starters, ignore the 'dmmy' package reference in the install logs, that is just a dumy command.2. From the logs, I beleive the error that is causing the failure is the failure to mount error, which means you specified exteranl storage type in postConfigure.    External storage types requires the user to setup mounts in /etc/fstab or manually on the command line to mount to the data directories. Check the installtion    documenetaion for further information.    If you don't have external storage and you want to store on the lcoal servers, then you will need to re-run postConfigure and specifcy 'internal' storage. David Hill  (InfiniDB)

[/quote]

 

 

Hi David, I have same problem and same error, but I specified 'internal' storage.

Can You help me?

 

P.S. poblem on Suse

all fine on Linux

marinakr
marinakr's picture
Offline
Last seen: 2 months 2 weeks ago
Joined: Dec 27 2013
Junior Boarder

Posts: 6

Marina Victoria
Error
0.1 port: 8604         
May  7 16:34:52 xfarm oamcpp[17575]: 52.603164 |0|0|0| E 08 CAL0000: getSystemStatus: MessageQueueClient exception: API Failure return in getSystemStatus API         
May  7 16:35:12 xfarm IDBFile[22937]: 12.885990 |0|0|0| E 35 CAL0002: Failed to open file: /usr/local/Calpont/data1/systemFiles/dbrm/BRM_saves_current, exception: unable to open Buffered file  
May  7 16:38:18 xfarm ProcessManager[23003]: 18.114957 |0|0|0| E 17 CAL0000: line: 2816 EXCEPTION ERROR on getProcessStatus: API Failure return in getProcessStatus API       
May  7 16:38:28 xfarm ProcessManager[23003]: 28.077693 |0|0|0| E 17 CAL0000: line: 2816 EXCEPTION ERROR on getProcessStatus: API Failure return in getProcessStatus API
May  7 16:41:02 xfarm ProcessManager[23003]: 02.258990 |0|0|0| E 17 CAL0000: line: 2816 EXCEPTION ERROR on getProcessStatus: API Failure return in getProcessStatus API       
 
 
 
 

 

davidhill
davidhill's picture
Offline
Last seen: 1 day 1 hour ago
Joined: Oct 27 2009
Administrator

Posts: 595

david hill
DBRM open file issue

Marina, you issue is a bit different. Either the file doesn't exist or there is some form of permission problem reading it.

Maybe it didn't get created during install. If it doesn't exist, try the following command with the system ACTIVE:

 

# /usr/local/Calpont/bin/dbbuilder 7

 

This will either go create the file along with others, or tell you it's already created. If already created and you still have the problem, post the results of the following:

 

# ls -l /usr/local

# ls -l /usr/local/Calpont/data1/systemFiles/

 

David

marinakr
marinakr's picture
Offline
Last seen: 2 months 2 weeks ago
Joined: Dec 27 2013
Junior Boarder

Posts: 6

Marina Victoria
DBRM open file issue

Thank You!