Rootop 服务器运维与web架构

2011-10-09
发表者 Venus
暂无评论

Verifying DMI pool DATA

     硬件完全没有没问，刚配置的新机，然后安装系统过程中，强制重启一次（在分区的时候）。

然后自检过后，停留在 Verifying DMI pool DATA ，清除CMOS信息也不好用，最后想到可能是硬盘分区或者是引导信息的问题，拿盘，光驱启动，重新分区··· 即可。

2011-09-30
发表者 Venus
暂无评论

Linux下更改系统时区及时间

       装了一台测试机，发现时区不是CST：   //CST china standard time

[root@localhost ~]# date
Fri Apr 14 23:26:05 EDT 2006                 //EDT (美国)东区时区

[root@localhost ~]# date -s 2011/9/30
Fri Sep 30 00:00:00 EDT 2011
[root@localhost ~]# date -s 14:18
Fri Sep 30 14:18:00 EDT 2011
[root@localhost ~]# date
Fri Sep 30 14:18:01 EDT 2011
[root@localhost ~]# hwclock -w

/usr/share/zoneinfo/Asia/ 下保存着系统各个时区信息

/etc/localtime 保存当前系统时区及时间信息

[root@localhost ~]# cd /usr/share/zoneinfo/Asia/
Aden           Colombo        Karachi        Oral           Tbilisi
Almaty         Dacca          Kashgar        Phnom_Penh     Tehran
Amman          Damascus       Kathmandu      Pontianak      Tel_Aviv
Anadyr         Dhaka          Katmandu       Pyongyang      Thimbu
Aqtau          Dili           Kolkata        Qatar          Thimphu
Aqtobe         Dubai          Krasnoyarsk    Qyzylorda      Tokyo
Ashgabat       Dushanbe       Kuala_Lumpur   Rangoon        Ujung_Pandang
Ashkhabad      Gaza           Kuching        Riyadh         Ulaanbaatar
Baghdad        Harbin         Kuwait         Riyadh87       Ulan_Bator
Bahrain        Ho_Chi_Minh    Macao          Riyadh88       Urumqi
Baku           Hong_Kong      Macau          Riyadh89       Vientiane
Bangkok        Hovd           Magadan        Saigon         Vladivostok
Beirut         Irkutsk        Makassar       Sakhalin       Yakutsk
Bishkek        Istanbul       Manila         Samarkand      Yekaterinburg
Brunei         Jakarta        Muscat         Seoul          Yerevan
Calcutta       Jayapura       Nicosia        Shanghai
Choibalsan     Jerusalem      Novokuznetsk   Singapore
Chongqing      Kabul          Novosibirsk    Taipei
Chungking      Kamchatka      Omsk           Tashkent
[root@localhost ~]# cp  /usr/share/zoneinfo/Asia/Shanghai /etc/localtime
cp: overwrite `/etc/localtime’? y
[root@localhost ~]# date
Sat Oct  1 02:20:03 CST 2011       //更改为CST
[root@localhost ~]# date -R
Sat, 01 Oct 2011 02:21:45 +0800
然后重新设置下时间即可。

        我们也可以通过rh系统中的命令来修改：
[root@localhost ~]# tzselect           // tzselect – select a time zone

比较人性化，可以根据提示直接修改即可。

2011-09-29
发表者 Venus
暂无评论

linux下 mysql 查看及更改默认数据库引擎

       mysql 默认的数据库引擎是MyISAM，不支持事务和外键，也可使用支持事务和外键的InnoDB。

查看当前数据库的所支持的数据库引擎以及默认数据库引擎：

我服务器环境系统为：centos5.3  mysql版本为：5.0.45

 mysql> show engines;
+————+———-+——————————————————-                                          ———+
| Engine     | Support  | Comment                                                                                                  |
+————+———-+——————————————————-                                          ———+
| MyISAM     | DEFAULT  | Default engine as of MySQL 3.23 with great performance                                                   |
| MEMORY     | YES      | Hash based, stored in memory, useful for temporary tab                                          les      |
| InnoDB     | DISABLED | Supports transactions, row-level locking, and foreign                                           keys     |
| BerkeleyDB | DISABLED | Supports transactions and page-level locking                                                             |
| BLACKHOLE  | NO       | /dev/null storage engine (anything you write to it dis                                          appears) |
| EXAMPLE    | NO       | Example storage engine                                                                                   |
| ARCHIVE    | NO       | Archive storage engine                                                                                   |
| CSV        | NO       | CSV storage engine                                                                                       |
| ndbcluster | NO       | Clustered, fault-tolerant, memory-based tables                                                           |
| FEDERATED  | NO       | Federated MySQL storage engine                                                                           |
| MRG_MYISAM | YES      | Collection of identical MyISAM tables                                                                    |
| ISAM       | NO       | Obsolete storage engine                                                                                  |
+————+———-+——————————————————-                                          ———+
12 rows in set (0.00 sec)

mysql>

通过上面我们可以发现，默认的数据库引擎是MyISAM ，在support中，显示为YES的为支持，NO为不支持，DEFAULT为默认，DISABLED为关闭，InooDB可以在my.cnf中配置开启：

注释掉my.cnf配置文件中“skip-innodb ”部分，保存重启服务。

再次查看，DISABLED就显示为YES了。

然后在my.cnf中[mysqld] 部分添加代码：

default-storage-engine=InnoDB

重启mysqld，再次show engines 确认。

数据库引擎默认就更改为InnoDB。

在windows环境中，数据库默认引擎为InnoDB，也可以通过修改my.ini 来定义默认引擎。方法一样。

PS：

在linux中的my.cnf配置文件中有这么一段：

# Uncomment the following if you are using InnoDB tables
#innodb_data_home_dir = /var/lib/mysql/
#innodb_data_file_path = ibdata1:10M:autoextend
#innodb_log_group_home_dir = /var/lib/mysql/
#innodb_log_arch_dir = /var/lib/mysql/
# You can set .._buffer_pool_size up to 50 – 80 %
# of RAM but beware of setting memory usage too high
#innodb_buffer_pool_size = 16M
#innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
#innodb_log_file_size = 5M
#innodb_log_buffer_size = 8M
#innodb_flush_log_at_trx_commit = 1
#innodb_lock_wait_timeout = 50

使用InnoDB引擎的建议取消注释，以优化数据库性能。

2011-09-28
发表者 Venus
暂无评论

This error can be caused by a virtual directory not being configured as an application in IIS

Server Error in ‘/’ Application.
——————————————————————————–

Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message: It is an error to use a section registered as allowDefinition=’MachineToApplication’ beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS.

Source Error:
Line 35:         –>
Line 36:     <globalization requestEncoding=”GB2312″ responseEncoding=”GB2312″ fileEncoding=”GB2312″ culture=”zh-CN” uiCulture=”zh-CN”/>
Line 37:     <sessionState timeout=”30″ cookieless=”false” stateConnectionString=”tcpip=127.0.0.1:42424″ mode=”InProc” >
Line 38:     </sessionState>
Line 39:     <compilation debug=”true”>
 

Source File: D:\client\website\web.config    Line: 37

Show Additional Configuration Errors:
It is an error to use a section registered as allowDefinition=’MachineToApplication’ beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. (D:\client\website\web.config line 61)
It is an error to use a section registered as allowDefinition=’MachineToApplication’ beyond application level.  This error can be caused by a virtual directory not being configured as an application in IIS. (D:\client\website\web.config line 91)
                     
 
——————————————————————————–
Version Information: Microsoft .NET Framework Version:2.0.50727.3623; ASP.NET Version:2.0.50727.3618

检查你的网站根目录路径是否配置正确！

网络资料：

This error can be caused by a virtual directory not being configured as an application in IIS

这个报错一般是由于两种原因引起的。

1 是由于您没有为目录创建一个Application

如果你用的是空间商提供的虚拟空间，出现这样的问题很可能是你的空间配置问题，一般虚拟空间都会提供给你一个增加虚拟文件夹的功能。

2 是由于您在站点的子目录中的web.config中加入了只能在根目录中配置的信息。如Session或是权限。

具体的解决方法如下：

You may get this error when trying to browse an asp.net application.

The debug information shows that “This error can be caused by a virtual directory not being configured as an application in IIS.”

However, this error occurs primarily out of 2 scenarios.

1. When you create an new web application using visual studio.net, it automatically creates the virtual directory and configures it as an application. However, if you manually create the virtual directory and it is not configured as an application, then you will not be able to browse the application and may get the above error. The debug information you get as mentioned above, is applicable to this scenario.

To resolve it, Right Click on the virtual directory – select properties and then click on
“Create” next to the “Application” Label and the textbox. It will automatically create the “application” using the virtual directory’s name. Now the application can be accessed.

2. When you have sub-directories in your application, you can have web.config file for the sub-directory. However, there are certain properties which cannot be set in the web.config of the sub-directory such as authentication, session state (you may see that the error message shows the line number where the authentication or sessionstate is declared in the web.config of the sub-directory). The reason is, these settings cannot be overridden at the sub-directory level unless the sub-directory is also configured as an application (as mentioned in the above point).

Mostly we have the practice of adding web.config in the sub-directory if we want to protect access to the sub-directory files (say, the directory is admin and we wish to protect the admin pages from unathorized users).

But actually, this can be achieved in the web.config at the application’s root level itself, by specifing the location path tags and authorization, as follows:-

<location path=”Admin”>

      <system.web>

        <authorization>

<allow roles=”administrators” />

<deny users=”*” />

        </authorization>

      </system.web>

</location>

However, if you wish to have a web.config at the sub-directory level and protect the sub-directory, you can just specify the Authorization mode as follows:-

<configuration>
<system.web>
<authorization>
       <allow roles=”administrators” />
       <deny users=”*” />
</authorization>
</system.web>
</configuration>