Hi Shivakeerthi,
 
Are you doing "yum update" on these Fedora system?  You may be hitting a
variation of XX-6483. 
 
The problem is with the sipxecs-release-4.0.1 RPM in our repository.
(The repo is needed for dependency RPMs, such as nsis and xerces.)
Unfortunately the sipxecs-release-4.0.1 RPM is tagged as obsolescing
"fedora-release".  So, I think a "yum update" will remove your Fedora
repos, in addition to installing sipxecs-release-4.0.1, which has
hard-coded pointers to the CentOS 5.2 repo.  Possibly this is corrupting
your Fedora installation.  (We had a couple of systems here stop
responding to keyboard input, likely due to this problem.)
 
For now, re-install Fedora 10 in the broken machines, and simply avoid
using "yum update".  



-Paul 
[email protected] 




________________________________

        From: Basappa Vamadevappa, Shivakeerthi (AMR:7809) 
        Sent: October 12, 2009 2:21 AM
        To: Mossman, Paul (CAR:9D30); '[email protected]'
        Subject: RE: [sipX-dev] Build Issue
        
        
        Hi Paul,
         
        After doing step 4, system was not responding so I tried with
option of rebooting the system. After rebooting,  basic fedora system
has to come up but it shows the line for fedora booting up screen and
stops. I have not modified, any environment variable.
         
        These are some of the steps which could be reason for this
problem 
        1. Compilation failure after updating the code ('svn up main'):

        Solution: This might be because some of the directory structures
might be changed or the files might be moved from one directory to the
other in the latest code that u had checked out.

        So, just re-run the step 4 and step 5 of EDE Setup mentioned in
the below link.

        
http://sipx-wiki.calivia.com/index.php/Express_Development_Environment_S
etup
<http://sipx-wiki.calivia.com/index.php/Express_Development_Environment_
Setup> 

        Also, while running step 4 make sure that u delete the old
ede_build_devuser.sh file in the WORKING directory. Otherwise, when u do
wget it will download the latest ede_build_devuser.sh and rename it as
ede_build_devuser.sh.1. So, when u try to run this script by invoking
./ede_build_devuser.sh , u will run the old script and this might cause
the system to crash.

        I think this was the reason for some of the EDE system crashes
that we faced couple of times.

        2. What to do when you have messed up with your local copy of
sepXecs code base or you have accidently deleted some files/directories?

        Solution: To solve this, just update your local code base and
when you get any conflicts during updation, select the option to accept
their version of entire file (Option: tf: theirs-full). This will copy
the file from the repository to ur local code base whenever there is a
conflict between ur file and the remote copy.

        Command: svn up ~/WORKING/main

        (For conflicts, enter the option 'tf ' )

        After updating the code base, compile the code and if it gives
error follow the solution mentioned above in 1.

        Thanks,

        Shivakeerthi

         
         
        
        
________________________________

        From: Mossman, Paul (CAR:9D30) 
        Sent: Thursday, October 01, 2009 8:00 PM
        To: [email protected]
        Cc: Basappa Vamadevappa, Shivakeerthi (AMR:7809)
        Subject: RE: [sipX-dev] Build Issue
        
        
        Hi Shivakeerthi,
         
        Sorry, I must have have skipped reading this post from last
week.
         
        The c. problem was likely caused by a bug in the code, as you
suggest.
         
        Rather than remove everything and re-start be getting new source
(Step 3), you could have just updated your source and re-ran the Step 4
script.  (Maybe that's what you mean by b.?)
         
        Either way will give you the same end result, the Step 4 script
should complete.
         
        But what happened after that?  What prompted you to reboot?  In
what way is the system now corrupted and unusable?
         
        (You didn't happen to mess with your $JAVA_HOME environment
variable did you?)
        


        -Paul 
        [email protected] 


________________________________

                From: [email protected]
[mailto:[email protected]] On Behalf Of Basappa
Vamadevappa, Shivakeerthi (AMR:7809)
                Sent: September 23, 2009 7:33 AM
                To: [email protected]
                Subject: [sipX-dev] Build Issue
                
                

                Hi, 

                I created SDE using the below link 

        
http://sipx-wiki.calivia.com/index.php/Express_Development_Environment_S
etup
<http://sipx-wiki.calivia.com/index.php/Express_Development_Environment_
Setup>  

                Below steps are caused the system to crash, and after
rebooting system is not coming up. 

                a. Installed SDE using the above link. 
                b. Execute svn up in main directory. 
                c. After compilation and install, I saw version mismatch
error for some of the services (same as mentioned in the CR XX-5827)

                d. Because of this I could not proceed further, so I
removed the working directory and started from Step 3 which is mentioned
in SDE link above.

                e. Reboot the system, and it got corrupted. Not able to
use the system. 

                Here am I doing something wrong? If so, Please suggest
me. 

                Thanks, 
                Shivakeerthi 

_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/

Reply via email to