svn提交时出现(413 Request Entity Too Large)错误解决方法

1、visual svn server安装在windows服务器上
2、windows服务器在内网，在windows的前面放置了一台Linux服务器，然后用nginx做的反向代理
3、visual svn server 使用的是8080端口，配置nginx反向代理文件

在svn提交的时候报错 Unexpected HTTP status 413 'Request Entity Too Large' on

是因为nginx配置反向代理时候，client_max_body_size 不够大导致的。

修改nginx反向代理的配置文件

ubuntu 14.04 的 dns nameserver

ubuntu 14.04 的DNS设置不能再用 /etc/resolv.conf 来管理

If you are using ubuntu 14.04, you may find you can not setting dns on your /etc/resolv.conf

This is because ubuntu using resolvconf to manage the dns setting, every times system boot, resolvconf will regenerate resolv.conf file.

But there always have way to do this.

vim /etc/resolvconf/resolv.conf.d/head  

在最新的ubuntu 14.04中，/etc/resolv.conf 在系统重启之后，会被重新生成，这样你原来配置的DNS就消失了，但是，你可以设置

Linux iptables

http://vbird.dic.ksu.edu.tw/linux_server/0250simple_firewall_3.php#netfilter_chain

Linux 的 iptables 至少就有三个表格，包括管理本机进出的 filter 、管理后端主机 (防火墙内部的其他计算机) 的 nat 、管理特殊旗标使用的 mangle (较少使用) 。更有甚者，我们还可以自定义额外的链呢！ 真是很神奇吧！每个表格与其中链的用途分别是这样的：

• filter (过滤器)：主要跟进入 Linux 本机的封包有关，这个是预设的 table 喔！
  • INPUT：主要与想要进入我们 Linux 本机的封包有关；
  • OUTPUT：主要与我们 Linux 本机所要送出的封包有关；
  • FORWARD：这个咚咚与 Linux 本机比较没有关系， 他可以『转递封包』到后端的计算机中，与下列 nat table 相关性较高。
• nat (地址转换)：是 Network Address Translation 的缩写， 这个表格主要在进行来源与目的之 IP 或 port 的转换，与 Linux 本机较无关，主要与 Linux 主机后的局域网络内计算机较有相关。
  • PREROUTING：在进行路由判断之前所要进行的规则(DNAT/REDIRECT)
  • POSTROUTING：在进行路由判断之后所要进行的规则(SNAT/MASQUERADE)
  • OUTPUT：与发送出去的封包有关
• mangle (破坏者)：这个表格主要是与特殊的封包的路由旗标有关， 早期仅有 PREROUTING 及 OUTPUT 链，不过从 kernel 2.4.18 之后加入了 INPUT 及 FORWARD 链。 由于这个表格与特殊旗标相关性较高，所以像咱们这种单纯的环境当中，较少使用 mangle 这个表格。

如果你在安装的时候选择没有防火墙的话，那么 iptables 在一开始的时候应该是没有规则的，不过， 可能因为你在安装的时候就有选择系统自动帮你建立防火墙机制，那系统就会有默认的防火墙规则了！ 无论如何，我们先来看看目前本机的防火墙规则是如何吧！

[root@www ~]# iptables [-t tables] [-L] [-nv] 选项与参数： -t ：后面接 table ，例如 nat 或 filter ，若省略此项目，则使用默认的 filter -L ：列出目前的 table 的规则 -n ：不进行 IP 与 HOSTNAME 的反查，显示讯息的速度会快很多！ -v ：列出更多的信息，包括通过该规则的封包总位数、相关的网络接口等 范例：列出 filter table 三条链的规则 [root@www ~]# iptables -L -n Chain INPUT (policy ACCEPT) <==针对 INPUT 链，且预设政策为可接受 target prot opt source destination <==说明栏 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED <==第 1 条规则 ACCEPT icmp -- 0.0.0.0/0 0.0.0.0/0 <==第 2 条规则 ACCEPT all -- 0.0.0.0/0 0.0.0.0/0 <==第 3 条规则 ACCEPT tcp -- 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22 <==以下类推 REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain FORWARD (policy ACCEPT) <==针对 FORWARD 链，且预设政策为可接受 target prot opt source destination REJECT all -- 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited Chain OUTPUT (policy ACCEPT) <==针对 OUTPUT 链，且预设政策为可接受 target prot opt source destination 范例：列出 nat table 三条链的规则 [root@www ~]# iptables -t nat -L -n Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination

在上表中，每一个 Chain 就是前面提到的每个链啰～ Chain 那一行里面括号的 policy 就是预设的政策， 那底下的 target, prot 代表什么呢？

• target：代表进行的动作， ACCEPT 是放行，而 REJECT 则是拒绝，此外，尚有 DROP (丢弃) 的项目！
• prot：代表使用的封包协议，主要有 tcp, udp 及 icmp 三种封包格式；
• opt：额外的选项说明
• source ：代表此规则是针对哪个『来源 IP』进行限制？
• destination ：代表此规则是针对哪个『目标 IP』进行限制？

在输出结果中，第一个范例因为没有加上 -t 的选项，所以默认就是 filter 这个表格内的 INPUT, OUTPUT, FORWARD 三条链的规则啰。若针对单机来说，INPUT 与 FORWARD 算是比较重要的管制防火墙链， 所以你可以发现最后一条规则的政策是 REJECT (拒绝) 喔！虽然 INPUT 与 FORWARD 的政策是放行 (ACCEPT)， 不过在最后一条规则就已经将全部的封包都拒绝了！

不过这个指令的观察只是作个格式化的查阅，要详细解释每个规则会比较不容易解析。举例来说， 我们将 INPUT 的 5 条规则依据输出结果来说明一下，结果会变成：

1. 只要是封包状态为 RELATED,ESTABLISHED 就予以接受
2. 只要封包协议是 icmp 类型的，就予以放行
3. 无论任何来源 (0.0.0.0/0) 且要去任何目标的封包，不论任何封包格式 (prot 为 all)，通通都接受
4. 只要是传给 port 22 的主动式联机 tcp 封包就接受
5. 全部的封包信息通通拒绝

Ubuntu 开机 waiting for network configuration

安装好ubuntu server 之后，配置了两块网卡，ip配置是修改interface文件来完成，可是在启动的时候总是显示
“Waiting for network configuration…”和”Waiting up to 60 more seconds for network configuration…”，每次在这都要等待快2分钟，好是烦人，下面给出解决办法

在终端中输入

1 2 3 4 5 6 7 8

sudo vim /etc/init/failsafe.conf     $PLYMOUTH message --text="Waiting for network configuration..." || :     sleep 1       $PLYMOUTH message --text="Waiting up to 60 more seconds for network configuration..." || :     sleep 1

将上面两处的sleep后面的数字修改成1，就是只等待1秒，这样就会快多了

ubuntu 14.04 service networking restart 无法重启

更改了 /etc/network/interfaces

要重启一下网卡，使其生效

使用命令 service networking restart 无法重启，并报错

stop: Job failed while stopping
start: Job is already running: networking


原因：
This was never a supported way to bounce the network, starting with 14.04, we changed the init script to fail rather than possibly trash your machine.

If you look at upstart's log, you'll notice the following message:
Stopping or restarting the networking job is not supported.
Use ifdown & ifup to reconfigure desired interface.


在 14.04 版本中，取消了 service networking restart 的功能，只能使用 ifdown和ifup 来重新配置网卡接口

SQL SERVER 2008 r2 sa和windows账号都无法登录

处理方式:

1. 停止正在运行的sql server服务；
2. 在cmd中切换到sql server目录中的Binn目录(如果这个路径在path环境变量中不切换也行)，运行sqlservr.exe -m，注-m为单用户模式的参数，这个cmd窗口不能关闭；
3. 新打开一个cmd窗口，执行如下语句，如果你知道是什么意思，这一步可以用Microsoft SQL Server Management Studio来代替，(以下操作sqlcmd.exe所在路径在path环境变量中):
   C:\Users\Administrator>sqlcmd
   1> create login tempsa with password='tempsa@123'
   2> go
   1> sp_addsrvrolemember 'tempsa','sysadmin'
   2> go
4. 关闭这两个cmd窗口，启动sql server服务，使用上一步创建的用户登录，重置/修改一下sa的密码，这时sa就可以登录了

System.ServiceModel.Activation.HttpModule

.NET 安装的顺序应该是先装 IIS，再装 VS.NET，如果次序反了，或者 IIS重装了，就需要使用aspnet_regiis.exe -i 来重新安装 IIS Mapping（主要用于aspx, asmx等文件的 Extention 的匹配）。在 C:\WINDOWS\Microsoft.NET\Framework\v1.0.3705 目录下，运行下面的命令：aspnet_regiis.exe -i。


报错：不能加载 System.ServiceModel.Activation.HttpModule
Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: System.TypeLoadException: Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′.Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′. Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more inform ation about the eraaaaaror and where it originated in the code. Exception Details: System.TypeLoadException: Could not load type ‘System.ServiceModel.Activation.HttpModule’ from assembly ‘System.ServiceModel, Version=3.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089′.

解决方法：
使用命令： c:\WINDOWS\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -iru

redmine2.5.1 点击我的帐户和个人设置出现500错误

http://www.linuxidc.com/Linux/2013-05/85201.htm

安装redmine 2.5.1，因为之前搭过，所以搭建过程还算顺利，但是搭完之后发现了问题，后台登陆之后，点击“我的帐户”，及“管理”-》“设置”据报错。

页面提示Internal error，页面的title是redmine 500 error。

ruby 的版本是 1.9.3

后来查找到另外一种解决方案，终于解决了我的问题，如下，供大家参考。

#cd /var/www/redmine
#vi app/helpers/application_helper.rb

找到以下内容，进行相应的删除或添加。

  def lang_options_for_select(blank=true)
    (blank ? [["(auto)", ""]] : []) + languages_options  //删除此行
    (blank ? [["(auto)", ""]] : []) +                    //添加此行
      valid_languages.collect{|lang| [ ll(lang.to_s, :general_lang_name), lang.to_s]}.sort{|x,y| x.last <=> y.last }  //添加此行
  end

#vi lib/redmine/i18n.rb

找到以下内容，并全部删除。

    # Returns an array of languages names and code sorted by names, example:
    # [["Deutsch", "de"], ["English", "en"] ...]
    #
    # The result is cached to prevent from loading all translations files.
    def languages_options
      ActionController::Base.cache_store.fetch "i18n/languages_options" do
        valid_languages.map {|lang| [ll(lang.to_s, :general_lang_name), lang.to_s]}.sort {|x,y| x.first <=> y.first }
      end     
    end

# vi test/unit/lib/redmine/i18n_test.rb

找到以下内容，并全部删除。

  def test_languages_options
    options = languages_options

    assert options.is_a?(Array)
    assert_equal valid_languages.size, options.size
    assert_nil options.detect {|option| !option.is_a?(Array)}
    assert_nil options.detect {|option| option.size != 2}
    assert_nil options.detect {|option| !option.first.is_a?(String) || !option.last.is_a?(String)}
    assert_include ["English", "en"], options
  end

nginx auth basic 认证

有时候需要象Apache那样为指定的目录添加访问验证，一般在Apache下使用htpasswd来添加，而htpasswd是包含在apache2-utils里


以一个简单的后台管理为例， 地址：http://xxxx/admin/*, 对admin 下面的文件进行权限管理
1. 使用命令生成passfile 文件： htpasswd -c -d /etc/nginx/pass_file  username

2. 修改ngnix 配置

location ~ /admin {
        auth_basic "Restricted";
        auth_basic_user_file /etc/nginx/pass_file; //请使用绝对路径
        root   /home/www/admin; //host 地址，不然认证通过之后，找不到对应的文件
}  

htpasswd命令

apache htpasswd 命令选项参数说明

　　-c 创建一个加密文件

　　-n 不更新加密文件，只将apache htpasswd命令加密后的用户名密码显示在屏幕上

　　-m 默认apache htpassswd命令采用MD5算法对密码进行加密

　　-d apache htpassswd命令采用CRYPT算法对密码进行加密
　　-p apache htpassswd命令不对密码进行进行加密，即明文密码

　　-s apache htpassswd命令采用SHA算法对密码进行加密

　　-b 在apache htpassswd命令行中一并输入用户名和密码而不是根据提示输入密码
　　-D 删除指定的用户

apache htpasswd命令用法实例

1、利用htpasswd命令添加用户

　　htpasswd -bc passwd_filename username 123456

2、在原有密码文件中增加下一个用户

　　htpasswd -b passwd_filename username 123456

3、如何不更新密码文件，只显示加密后的用户名和密码

　　htpasswd -nb username 123456

4、利用htpasswd命令删除用户名和密码

　　htpasswd -D passwd_filename username

5、利用htpasswd命令修改密码

　　htpasswd -D passwd_filename username

　　htpasswd -b passwd_filename username 5678

HTTP 错误 403.14 - Forbidden

重新注册asp.net4.0

1、返回的错误表明IIS缺少针对无后缀的MVC请求的映射，ASP.NET处理程序无法接收到请求。

2、要解决这个问题，首先确保ASP.NET MVC3已安装好，然后检查站点的处理程序映射，看是否存在下列映射：
ExtensionlessUrlHandler-Integrated-4.0
ExtensionlessUrlHandler-ISAPI-4.0_32bit
ExtensionlessUrlHandler-ISAPI-4.0_64bit

3、如果映射存在，请检查应用程序是否分配给了.NET Framework4.0的应用程序池。

4、如果映射不存在，你可以以管理员运行下面的命令注册：
32位机器：
C:\Windows\Microsoft.NET\Framework\v4.0.30319\aspnet_regiis.exe -i
64位机器：
C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe -i

MySql.Data.MySqlClient.MySqlException: Too many connections

web程序在访问mysql数据库时报错

MySql.Data.MySqlClient.MySqlException: Too many connections

1、要先关闭IIS进程
2、关闭mysql进程，找到mysql服务，右键转到mysql进程，kill掉。
3、重新启动IIS
4、重新启动mysql服务

customErrors tag should then have its "mode" attribute set to "Off"

测试报错的接口，然后在PC端上访问时，报错为 webconfig 的一些信息。


页面报错信息：

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine. 

Details: To enable the details of this specific error message to be viewable on remote machines, please create a tag within a "web.config" configuration file located in the root directory of the current web application. This tag should then have its "mode" attribute set to "Off".

详细信息: 若要使他人能够从本地服务器计算机上查看此特定错误信息的详细信息，请在位于当前 Web 应用程序根目录下的“web.config”配置文件中创建一个 customErrors 标记。然后应将此 customErrors 标记的“mode”属性设置为“RemoteOnly”。若要使他人能够在远程计算机上查看详细信息，请将“mode”设置为“Off”。

注释: 通过修改应用程序的 customErrors 配置标记的“defaultRedirect”属性，使之指向自定义错误页的 URL，可以用自定义错误页替换所看到的当前错误页。

其实际的意思就是，在PC端测试API时，出于安全原因，出现的内部服务器错误无法显示详细的信息，但是你可以在服务器端用浏览器测试API，来查看错误的详细信息。
但是，如果你非要在PC端测试API时，显示错误的详情，你也可以修改webconfig文件，添加 customErrors 标记。

当然，这样是很不安全的。

所以，报错页面弹出了webconfig的一些信息，实际上并不是webconfig的问题。



页面报错截图：

Ubuntu 安装 OpenERP 7.0

http://www.theopensourcerer.com/2012/12/how-to-install-openerp-7-0-on-ubuntu-12-04-lts/

Introduction

Welcome to the latest of our very popular OpenERP installation “How Tos”.

The new release of OpenERP 7.0 is a major upgrade and a new Long Term Support release; the 7.0 Release Notes extend to over 90 pages! The most noticeable change is a complete re-write of the User Interface that features a much more modern look and feel.

OpenERP 7.0 is not only better looking and easier to use, it also brings many improvements to the existing feature-set and adds a number of brand new features which extend the scope of the business needs covered by OpenERP. Integration of social network capabilities, integration with Google Docs and LinkedIn, new Contract Management, new Event Management, new Point of Sale, new Address Book, new Fleet Management,… are only some of the many enhancements in OpenERP 7.0.

The How To

Following that introduction, I bet you can’t wait to get your hands dirty…

Just one thing before we start: You can simply download a “.deb” package of OpenERP and install that on Ubuntu. Unfortunately that approach doesn’t provide us (Libertus Solutions) with enough fine-grained control over where things get installed, and it restricts our flexibility to modify & customise, hence I prefer to do it a slightly more manual way (this install process below should only take about 10-15 minutes once the host machine has been built).

So without further ado here we go:

Step 1. Build your server

I install just the bare minimum from the install routine (you may want to install the openssh-server during the install procedure or install subsequently depending on your needs).

After the server has restarted for the first time I install the openssh-server package (so we can connect to it remotely) and denyhoststo add a degree of brute-force attack protection. There are other protection applications available: I’m not saying this one is the best, but it’s one that works and is easy to configure and manage. If you don’t already, it’s also worth looking at setting up key-based ssh access, rather than relying on passwords. This can also help to limit the potential of brute-force attacks. [NB: This isn't a How To on securing your server...]

sudo apt-get install openssh-server denyhosts

Now make sure your server has all the latest versions & patches by doing an update:

sudo apt-get update
sudo apt-get dist-upgrade

Although not always essential it’s probably a good idea to reboot your server now and make sure it all comes back up and you can login via ssh.

Now we’re ready to start the OpenERP install.

Step 2. Create the OpenERP user that will own and run the application

sudo adduser --system --home=/opt/openerp --group openerp

This is a “system” user. It is there to own and run the application, it isn’t supposed to be a person type user with a login etc. In Ubuntu, a system user gets a UID below 1000, has no shell (it’s actually /bin/false) and has logins disabled. Note that I’ve specified a “home” of/opt/openerp, this is where the OpenERP server code will reside and is created automatically by the command above. The location of the server code is your choice of course, but be aware that some of the instructions and configuration files below may need to be altered if you decide to install to a different location.

[Note: If you want to run multiple versions of OpenERP on the same server, the way I do it is to create multiple users with the correct version number as part of the name, e.g. openerp70, openerp61 etc. If you also use this when creating the Postgres users too, you can have full separation of systems on the same server. I also use similarly named home directories, e.g. /opt/openerp70, /opt/openerp61 and config and start-up/shutdown files. You will also need to configure different ports for each instance or else only the first will start.]

A question I have been asked a few times is how to run the OpenERP server as the openerp system user from the command line if it has no shell. This can be done quite easily:

sudo su - openerp -s /bin/bash

This will su your current terminal login to the openerp user (the “-” between su and openerp is correct) and use the shell /bin/bash. When this command is run you will be in openerp’s home directory: /opt/openerp.

When you have done what you need you can leave the openerp user’s shell by typing exit.

Step 3. Install and configure the database server, PostgreSQL

sudo apt-get install postgresql

Then configure the OpenERP user on postgres:

First change to the postgres user so we have the necessary privileges to configure the database.

sudo su - postgres

Now create a new database user. This is so OpenERP has access rights to connect to PostgreSQL and to create and drop databases. Remember what your choice of password is here; you will need it later on:

createuser --createdb --username postgres --no-createrole --no-superuser --pwprompt openerp
Enter password for new role: ********
Enter it again: ********

Finally exit from the postgres user account:

exit

Step 4. Install the necessary Python libraries for the server

sudo apt-get install python-dateutil python-docutils python-feedparser python-gdata \
python-jinja2 python-ldap python-libxslt1 python-lxml python-mako python-mock python-openid \
python-psycopg2 python-psutil python-pybabel python-pychart python-pydot python-pyparsing \
python-reportlab python-simplejson python-tz python-unittest2 python-vatnumber python-vobject \
python-webdav python-werkzeug python-xlwt python-yaml python-zsi

With that done, all the dependencies for installing OpenERP 7.0 are now satisfied (note that there are some new packages required since 6.1).

Step 5. Install the OpenERP server

I tend to use wget for this sort of thing and I download the files to my home directory.

Make sure you get the latest version of the application: at the time of writing this it’s 7.0. I got the download links from their download pages(note there are also deb, rpm and exe builds in this area too). There isn’t a static 7.0 release tarball as such anymore, but there is a nightly build of the 7.0 source tree which should be just as good and will contain patches as and when things get fixed. The link below is to the source tarball for the 7.0 branch.

Note: As an alternative method of getting the code onto your server, Jerome added a very useful comment showing how to get it straight from launchpad. Thanks!

wget http://nightly.openerp.com/7.0/nightly/src/openerp-7.0-latest.tar.gz

Now install the code where we need it: cd to the /opt/openerp/ directory and extract the tarball there.

cd /opt/openerp
sudo tar xvf ~/openerp-7.0-latest.tar.gz

Next we need to change the ownership of all the the files to the OpenERP user and group we created earlier.

sudo chown -R openerp: *

And finally, the way I have done this is to copy the server directory to something with a simpler name so that the configuration files and boot scripts don’t need constant editing (I called it, rather unimaginatively, server). I started out using a symlink solution, but I found that when it comes to upgrading, it seems to make more sense to me to just keep a copy of the files in place and then overwrite them with the new code. This way you keep any custom or user-installed modules and reports etc. all in the right place.

sudo cp -a openerp-7.0 server

As an example, should OpenERP 7.0.1 come out soon, I can extract the tarballs into /opt/openerp/ as above. I can do any testing I need, then repeat the copy command so that the modified files will overwrite as needed and any custom modules, report templates and such will be retained. Once satisfied the upgrade is stable, the older 7.0 directories can be removed if wanted.

That’s the OpenERP server software installed. The last steps to a working system is to set up the configuration file and associated boot script so OpenERP starts and stops automatically when the server itself stops and starts.

Step 6. Configuring the OpenERP application

The default configuration file for the server (in /opt/openerp/server/install/) is actually very minimal and will, with only one small change work fine so we’ll simply copy that file to where we need it and change it’s ownership and permissions:

sudo cp /opt/openerp/server/install/openerp-server.conf /etc/
sudo chown openerp: /etc/openerp-server.conf
sudo chmod 640 /etc/openerp-server.conf

The above commands make the file owned and writeable only by the openerp user and group and only readable by openerp and root.

To allow the OpenERP server to run initially, you should only need to change one line in this file. Toward to the top of the file change the linedb_password = False to the same password you used back in step 3. Use your favourite text editor here. I tend to use nano, e.g.

sudo nano /etc/openerp-server.conf

One other line we might as well add to the configuration file now, is to tell OpenERP where to write its log file. To complement my suggested location below add the following line to the openerp-server.conf file:

logfile = /var/log/openerp/openerp-server.log

Once the configuration file is edited and saved, you can start the server just to check if it actually runs.

sudo su - openerp -s /bin/bash
/opt/openerp/server/openerp-server

If you end up with a few lines eventually saying OpenERP is running and waiting for connections then you are all set.

On my system I noticed the following warning:

2012-12-19 11:53:51,613 6586 WARNING ? openerp.addons.google_docs.google_docs: Please install latest gdata-python-client from http://code.google.com/p/gdata-python-client/downloads/list

The Ubuntu 12.04 packaged version of the python gdata client library is not quite recent enough, so to install a more up-to-date version I did the following (exit from the openerp user’s shell if you are still in it first):

sudo apt-get install python-pip
sudo pip install gdata --upgrade

Going back and repeating the commands to start the server resulted in no further warnings

sudo su - openerp -s /bin/bash
/opt/openerp/server/openerp-server

If there are errors, you’ll need to go back and find out where the problem is.

Otherwise simply enter CTL+C to stop the server and then exit to leave the openerp user account and go back to your own shell.

Step 7. Installing the boot script

For the final step we need to install a script which will be used to start-up and shut down the server automatically and also run the application as the correct user. There is a script you can use in /opt/openerp/server/install/openerp-server.init but this will need a few small modifications to work with the system installed the way I have described above. Here’s a link to the one I’ve already modified for 7.0.

Similar to the configuration file, you need to either copy it or paste the contents of this script to a file in /etc/init.d/ and call it openerp-server. Once it is in the right place you will need to make it executable and owned by root:

sudo chmod 755 /etc/init.d/openerp-server
sudo chown root: /etc/init.d/openerp-server

In the configuration file there’s an entry for the server’s log file. We need to create that directory first so that the server has somewhere to log to and also we must make it writeable by the openerp user:

sudo mkdir /var/log/openerp
sudo chown openerp:root /var/log/openerp

Step 8. Testing the server

To start the OpenERP server type:

sudo /etc/init.d/openerp-server start

You should now be able to view the logfile and see that the server has started.

less /var/log/openerp/openerp-server.log

If there are any problems starting the server you need to go back and check. There’s really no point ploughing on if the server doesn’t start…

OpenERP 7 Database Management Screen

If the log file looks OK, now point your web browser at the domain or IP address of your OpenERP server (or localhost if you are on the same machine) and use port 8069. The url will look something like this:

http://IP_or_domain.com:8069

What you should see is a screen like this one (it is the Database Management Screen because you have no OpenERP databases yet):

What I do recommend you do at this point is to change the super admin password to something nice and strong (Click the “Password” menu). By default this password is just “admin” and knowing that, a user can create, backup, restore and drop databases! This password is stored in plain text in the /etc/openerp-server.conf file; hence why we restricted access to just openerp and root. When you change and save the new password the /etc/openerp-server.conf file will be re-written and will have a lot more options in it.

Now it’s time to make sure the server stops properly too:

sudo /etc/init.d/openerp-server stop

Check the logfile again to make sure it has stopped and/or look at your server’s process list.

Step 9. Automating OpenERP startup and shutdown

If everything above seems to be working OK, the final step is make the script start and stop automatically with the Ubuntu Server. To do this type:

sudo update-rc.d openerp-server defaults

You can now try rebooting you server if you like. OpenERP should be running by the time you log back in.

If you type ps aux | grep openerp you should see a line similar to this:

openerp 1491 0.1 10.6 207132 53596 ? Sl 22:23 0:02 python /opt/openerp/server/openerp-server -c /etc/openerp-server.conf

Which shows that the server is running. And of course you can check the logfile or visit the server from your web browser too.

OpenERP 70 Main Setup Screen

That’s it! Next I would suggest you create a new database filling in the fields as desired. Once the database is initialised, you will be directed straight to the new main configuration screen which gives you a fell for the new User Interface in OpenERP 7 and shows you how easy it is to set up a basic system.